From: Markus Lidel <Markus.Lidel@shadowconnect•com>
To: Jeff Garzik <jeff@garzik•org>
Cc: Andi Kleen <ak@suse•de>,
chas@cmf•nrl.navy.mil, netdev@vger•kernel.org, kkeil@suse•de,
kai.germaschewski@gmx•de, isdn4linux@listserv•isdn4linux.de,
mac@melware•de, samuel@sortiz•org, Neela.Kolli@engenio•com,
linux-scsi@vger•kernel.org, Greg KH <greg@kroah•com>,
thomas@winischhofer•net
Subject: Re: [PATCH] Introduce BROKEN_ON_64BIT facility
Date: Mon, 02 Oct 2006 16:19:34 +0200 [thread overview]
Message-ID: <45211FF6.7090303@shadowconnect.com> (raw)
In-Reply-To: <4520E1CB.6070104@garzik.org>
Hello,
Jeff Garzik wrote:
> Andi Kleen wrote:
>> Jeff Garzik <jeff@garzik•org> writes:
>>> Add a broken-on-64bit option, similar to the existing broken-on-smp
>>> config option. This is just the first pass, marking the obvious
>>> candidates.
>> When I had this problem in the past I just used && !64BIT.
>> How is this new option different?
> Same reason why we have CONFIG_BROKEN_ON_SMP separate from CONFIG_SMP.
>> AFAIK I2O got fixed too. Do you have any evidence that it is really
>> broken on 64bit?
> i2o_config did not. Just read the code, it's obvious...
Although the documentation does say it need fixes, it really doesn't. It
is broken if used with 64-bit DMA addresses, but it does work on 64-bit
systems.
Best regards,
Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)
Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany
Phone: +49 82 82/99 51-0
Fax: +49 82 82/99 51-11
E-Mail: Markus.Lidel@shadowconnect•com
URL: http://www.shadowconnect.com
next prev parent reply other threads:[~2006-10-02 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 4:55 [PATCH] Introduce BROKEN_ON_64BIT facility Jeff Garzik
2006-10-02 9:51 ` Andi Kleen
2006-10-02 9:54 ` Jeff Garzik
2006-10-02 14:19 ` Markus Lidel [this message]
2006-10-02 13:03 ` Alan Cox
2006-10-02 13:52 ` chas williams - CONTRACTOR
2006-10-02 15:12 ` Alan Cox
2006-10-02 15:18 ` Matthew Wilcox
2006-10-02 16:21 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45211FF6.7090303@shadowconnect.com \
--to=markus.lidel@shadowconnect$(echo .)com \
--cc=Neela.Kolli@engenio$(echo .)com \
--cc=ak@suse$(echo .)de \
--cc=chas@cmf$(echo .)nrl.navy.mil \
--cc=greg@kroah$(echo .)com \
--cc=isdn4linux@listserv$(echo .)isdn4linux.de \
--cc=jeff@garzik$(echo .)org \
--cc=kai.germaschewski@gmx$(echo .)de \
--cc=kkeil@suse$(echo .)de \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=mac@melware$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
--cc=samuel@sortiz$(echo .)org \
--cc=thomas@winischhofer$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox