Thread: [Ndiswrapper-general] Re: Re: 64 bit support
Status: Beta
Brought to you by:
pgiri
From: Karl V. <kar...@se...> - 2004-06-21 20:55:52
|
Giridhar Pemmasani wrote: > On Mon, 21 Jun 2004 12:29:22 -0600, Eric Princen <epr...@bo...> > said: > > Eric> It's a good question whether or not the actual NT driver being > Eric> 32 bit will work with a 64 bit ndiswrapper driver. I'm 100% > > This question has been asked (and answered) before. The real problem > is getting a 64 bit windows driver. It is not clear if this driver, > when available, will follow the current NDIS. If it does, and when it > is available, making ndiswrapper 64-bit ready shouldn't be much of a > problem. But.. as I stated in my previous mail.. you don't need a 64-bit windows driver. I don't think the issue of getting the 32-bit windows driver to run in 64-bit Linux is that hard, considering you can run the x86_64 in 32-bit compatibility mode (the code to do this is already present in arch/x86_64/ia32/... albeit for usermode only -- but then.. does the windows 32 bit driver really NEED to be in kernel mode?!?!). Ofcourse.. preaching is way easier than doing :-) |
From: Eric P. <epr...@bo...> - 2004-06-21 21:16:08
|
That's not really my concern yet. It may well work just fine. What I'm trying to do is get ndiswrapper to compile 64 bit. I'm currently up against the fact that divdi3.c seems to be 32 bit only. I'm not sure what the file does or what can be done. It's not simply a matter of commenting out getSp and it's references. Thoughts on divdi3.c? On Mon, 2004-06-21 at 14:55, Karl Vogel wrote: > Giridhar Pemmasani wrote: > > > On Mon, 21 Jun 2004 12:29:22 -0600, Eric Princen <epr...@bo...> > > said: > > > > Eric> It's a good question whether or not the actual NT driver being > > Eric> 32 bit will work with a 64 bit ndiswrapper driver. I'm 100% > > > > This question has been asked (and answered) before. The real problem > > is getting a 64 bit windows driver. It is not clear if this driver, > > when available, will follow the current NDIS. If it does, and when it > > is available, making ndiswrapper 64-bit ready shouldn't be much of a > > problem. > > But.. as I stated in my previous mail.. you don't need a 64-bit windows > driver. I don't think the issue of getting the 32-bit windows driver to run > in 64-bit Linux is that hard, considering you can run the x86_64 in 32-bit > compatibility mode (the code to do this is already present in > arch/x86_64/ia32/... albeit for usermode only -- but then.. does the windows > 32 bit driver really NEED to be in kernel mode?!?!). > > Ofcourse.. preaching is way easier than doing :-) > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general |
From: Pontus F. <pon...@ta...> - 2004-06-22 06:47:27
|
On Mon, 2004-06-21 at 22:55, Karl Vogel wrote: > But.. as I stated in my previous mail.. you don't need a 64-bit windows > driver. I don't think the issue of getting the 32-bit windows driver to run > in 64-bit Linux is that hard, considering you can run the x86_64 in 32-bit > compatibility mode (the code to do this is already present in > arch/x86_64/ia32/... albeit for usermode only -- but then.. does the windows > 32 bit driver really NEED to be in kernel mode?!?!). > > Ofcourse.. preaching is way easier than doing :-) Exactly. Take a look at what I asked on the AMD64 mailing list some time ago: http://www.x86-64.org/lists/discuss/msg04761.html So until you have written the infrastructure to run 32 bit code in a 64 bit kernel (which is possible but very hard given the answer I got) your time spent on trying to get ndiswrapper running is a complete waste of time. Sorry. Getting ndiswrapper working with 64 bit ndis drivers is a much more realistic way, but neither I nor Giri has access to 64 bit hardware so this is nothing that will happen any time soon unless some macho man steps forward and does the dirty work :) Pontus |
From: Morgan B. <atr...@ya...> - 2004-06-22 19:56:46
|
It appears that many of the issues with the emachines M6805 wireless (using a bcm94306) (including both very slow/not working connection and very slow computer operation) result from incorrect IRQ steering due to ACPI problems. These problems are fixed in kernel 2.6.7. Be sure to enable ACPI under power management, as well as Local APIC support and IO-APIC support under Processor features in your kernel. Also remove noapic and pci=noacpi from your kernel arguments if you had been using them. This has the nice side effect of processor scaling and other power management features finally working. Good luck . Many many thanks to Pontus Fuchs for helping me get this pinpointed, as well as layyze and possumjc on the gentoo boards! __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail |
From: Pontus F. <pon...@ta...> - 2004-06-23 07:18:51
|
On Tue, 2004-06-22 at 21:56, Morgan Brown wrote: > It appears that many of the issues with the emachines > M6805 wireless (using a bcm94306) (including both very > slow/not working connection and very slow computer > operation) result from incorrect IRQ steering due to > ACPI problems. These problems are fixed in kernel > 2.6.7. Be sure to enable ACPI under power management, > as well as Local APIC support and IO-APIC support Great news! Thanks. Pontus |