linux-mips
[Top] [All Lists]

Re: iptables/vmalloc issues on alchemy

To: Dan Malek <dan@embeddedalley.com>
Subject: Re: iptables/vmalloc issues on alchemy
From: Thiemo Seufer <ths@networkno.de>
Date: Fri, 29 Apr 2005 01:52:45 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <c145ddc72b875ec3833ceba1a849b156@embeddedalley.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <8230E1CC35AF9F43839F3049E930169A137228@yang.LibreStream.local> <c145ddc72b875ec3833ceba1a849b156@embeddedalley.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.9i
Dan Malek wrote:
> 
> On Apr 28, 2005, at 5:22 PM, Christian Gan wrote:
> 
> >..... Again it would be okay if I used
> >kmalloc or if I disabled CONFIG_64BIT_PHYS_ADDR.
> 
> An Au1500 or Au1550 isn't likely to work with this disabled.
> PCI and other peripherals exist in the 36-bit space, unless you
> disable them.  I suspect all of this got broken with the dynamic
> exception handler building.  Prior to that, I suspect it works
> fine.  I guess we need to do some regression testing ....

I took the code from 2.4 for 36bit support, without the means of testing
the result. There was no support for it in the 2.6 linux-mips.org CVS at
that time, but some people apparently had uncontributed patches.


Thiemo

<Prev in Thread] Current Thread [Next in Thread>