From: Lee Revell <rlrevell@joe-job.com>
To: Wouter de Waal <wrm@ccii.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FDDI on Linux kernel 2.6
Date: Tue, 24 Oct 2006 11:20:36 -0400 [thread overview]
Message-ID: <1161703237.3982.81.camel@mindpipe> (raw)
In-Reply-To: <5.0.0.25.2.20061024131939.05e4de70@alpha.ccii.co.za>
On Tue, 2006-10-24 at 13:19 +0200, Wouter de Waal wrote:
> The first customer eventually found that the driver does not work when
> the kernel is configured to use 64 bit memory addressing. This would
> obviously have to do with the pointer sizes used by the driver
> structure.
>
> They did not need 64 bit addressing, and solved their problem by
> reconfiguring their kernel for 32 bit addressing.
>
> Is it possible to configure things so that this issue is highlighted
> when the kernel is built?
Most drivers will work on 64 bit without modification. If it's not
possible to make the driver 64 bit clean, then make it depend on
!X86_64 (and any other 64 bit platform the hardware might be used on).
Lee
next prev parent reply other threads:[~2006-10-24 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 11:19 FDDI on Linux kernel 2.6 Wouter de Waal
2006-10-24 14:02 ` Alan Cox
2006-10-24 15:20 ` Lee Revell [this message]
2006-10-24 15:30 ` Maciej W. Rozycki
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=1161703237.3982.81.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wrm@ccii.co.za \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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