From: Jim Gifford <maillist@jg555.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: ralf@linux-mips.org, tbm@cyrius.com, pdh@colonel-panic.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH Cobalt 1/1] 64-bit fix
Date: Wed, 18 Jan 2006 09:59:54 -0800 [thread overview]
Message-ID: <43CE821A.6060004@jg555.com> (raw)
In-Reply-To: <20060117.232350.93019515.anemo@mba.ocn.ne.jp>
Atsushi Nemoto wrote:
> But got no response at that time. So I ask again. Could you tell us
> how the iomap patch broken verbosely, please?
>
>
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?
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
maillist@jg555.com
next prev parent reply other threads:[~2006-01-18 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 18:59 [PATCH Cobalt 1/1] 64-bit fix Peter Horton
2005-04-15 9:20 ` [OFF-TOPIC] Cobalt 64-bit, what for? (was: 64-bit fix) Dominique Quatravaux
2005-04-15 10:14 ` Ralf Baechle
2005-04-15 10:18 ` Dominic Sweetman
2005-04-15 10:25 ` Ralf Baechle
2006-01-16 15:45 ` [PATCH Cobalt 1/1] 64-bit fix Martin Michlmayr
2006-01-16 16:32 ` Jim Gifford
2006-01-16 16:50 ` Martin Michlmayr
2006-01-16 16:50 ` Martin Michlmayr
2006-01-17 13:51 ` Ralf Baechle
2006-01-17 14:23 ` Atsushi Nemoto
2006-01-18 17:59 ` Jim Gifford [this message]
2006-01-19 16:35 ` Atsushi Nemoto
2006-01-17 17:09 ` Jim Gifford
2006-01-17 13:29 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43CE821A.6060004@jg555.com \
--to=maillist@jg555.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=pdh@colonel-panic.org \
--cc=ralf@linux-mips.org \
--cc=tbm@cyrius.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox