Re: [solved] Yenta Cardbus allocation failure

2006-12-20 Thread Linus Torvalds
On Wed, 20 Dec 2006, Andrew Morton wrote: > > Linus has wondered "how much does Windows use"? How might we determine > that? Google knows everything, and finds, on MS own site no less: "Windows 2000 default resources: One 4K memory window One 2 MB memory window Two 256-byte I/O

Re: [solved] Yenta Cardbus allocation failure

2006-12-20 Thread Andrew Morton
On Tue, 19 Dec 2006 01:12:07 +0100 "Markus Rechberger" <[EMAIL PROTECTED]> wrote: > I went on with investigating that problem and found the problem, > though I'm not sure if that solution is acceptable.. > > seems like the memory range gets preallocated in setup-bus.c, and > CARDBUS_MEM_SIZE defi

Re: [solved] Yenta Cardbus allocation failure

2006-12-19 Thread Markus Rechberger
On 12/19/06, Chuck Ebbert <[EMAIL PROTECTED]> wrote: In-Reply-To: <[EMAIL PROTECTED]> On Tue, 19 Dec 2006 01:12:07 +0100, Markus Rechberger wrote: > I went on with investigating that problem and found the problem, > though I'm not sure if that solution is acceptable.. > > seems like the memory

Re: [solved] Yenta Cardbus allocation failure

2006-12-19 Thread Chuck Ebbert
In-Reply-To: <[EMAIL PROTECTED]> On Tue, 19 Dec 2006 01:12:07 +0100, Markus Rechberger wrote: > I went on with investigating that problem and found the problem, > though I'm not sure if that solution is acceptable.. > > seems like the memory range gets preallocated in setup-bus.c, and > CARDBUS_

Re: [solved] Yenta Cardbus allocation failure

2006-12-18 Thread Markus Rechberger
I went on with investigating that problem and found the problem, though I'm not sure if that solution is acceptable.. seems like the memory range gets preallocated in setup-bus.c, and CARDBUS_MEM_SIZE defines that size. I changed #define CARDBUS_MEM_SIZE(32*1024*1024) to #define CARDBUS_