|To:||Atsushi Nemoto <firstname.lastname@example.org>|
|Subject:||Re: [PATCH Cobalt 1/1] 64-bit fix|
|From:||Jim Gifford <email@example.com>|
|Date:||Wed, 18 Jan 2006 09:59:54 -0800|
|Cc:||firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com|
|References:||<20060116154543.GA26771@deprecation.cyrius.com> <43CBCAAE.firstname.lastname@example.org> <20060117135145.GE3336@linux-mips.org> <email@example.com>|
|User-agent:||Thunderbird 1.5 (Windows/20051201)|
Atsushi Nemoto wrote:
How can we get this resolved, this issue has been open a long time. Can we all work together to get a working solution in place that everyone will accept?But got no response at that time. So I ask again. Could you tell us how the iomap patch broken verbosely, please?
We all need to understand the concerns with the current method. The only issue I see from Ralf is the following:
Broken on multiple PCI busses.Now the way I understand the issue is the current iomap.c only handles a single bus, Ralf's point is that if there are multiple busses this patch may not work properly. Is that a correct statement Ralf.
So can't we have one iomap.c for single pci bus systems and one for multiple pci bus systems? Just a thought.
-- ---- Jim Gifford firstname.lastname@example.org
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: gdb gets confused with o32 core files, WANT_COMPAT_REG_H needed?, Ralf Baechle|
|Next by Date:||Cobalt Raq2 HD upgrade - Advice required, Dominique Quatravaux|
|Previous by Thread:||Re: [PATCH Cobalt 1/1] 64-bit fix, Atsushi Nemoto|
|Next by Thread:||Re: [PATCH Cobalt 1/1] 64-bit fix, Atsushi Nemoto|
|Indexes:||[Date] [Thread] [Top] [All Lists]|