linux-kernel - Re: FDDI on Linux kernel 2.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1161703237.3982.81.camel@mindpipe>
Date:	Tue, 24 Oct 2006 11:20:36 -0400
From:	Lee Revell <rlrevell@...-job.com>
To:	Wouter de Waal <wrm@...i.co.za>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: FDDI on Linux kernel 2.6

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/