linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: Sven Luther <sven.luther@wanadoo.fr>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Pegasos 2 support patch ...
Date: Wed, 30 Jun 2004 11:45:46 +0200	[thread overview]
Message-ID: <20040630094546.GA24491@pegasos> (raw)
In-Reply-To: <1088588447.28598.13.camel@localhost>


On Wed, Jun 30, 2004 at 10:40:47AM +0100, Adrian Cox wrote:
> On Wed, 2004-06-30 at 10:30, Sven Luther wrote:
> > On Wed, Jun 30, 2004 at 10:18:10AM +0100, Adrian Cox wrote:
> > > On Tue, 2004-06-29 at 17:50, Sven Luther wrote:
> > > > The remaining problem for the pegasos 2 is with the via82cxxx ide
> > > > driver, which needs to support a different irq for both channels, thus
> > > > breakign when a device is present on the second ide channel. [snip]
>
> > > My current idea is to add an extra flag to the ide_pci_device_t to
> > > indicate that the device defaults to ports 14 and 15, then modify
> > > ide_hwif_configure() to use this flag.
> >
> > Ok, sounds nice, do you plan to write this patch anytime soon, or should
> > i go forward and implement this idea ?
>
> I've got a few other things to get into the kernel before this, so
> please don't wait for me. If you make a patch I'll test it.

Ok, altough i have not much experience with ide stuff.

> In my case, the initial setup is that the device has been assigned I/O
> space address in the 0xfe00 range, and no PCI IRQ.  This confuses the
> PCI IDE code, because it assumes that the device must be an add-in card
> if it is not on the legacy ports.

Ok.

Friendly,

Sven Luther

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-30  9:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 16:50 Pegasos 2 support patch Sven Luther
2004-06-29 20:42 ` Sven Luther
2004-06-30  2:57   ` Benjamin Herrenschmidt
2004-06-30  6:00     ` Sven Luther
2004-06-30  8:10       ` Geert Uytterhoeven
2004-06-30  8:21         ` Sven Luther
2004-06-30  9:18 ` Adrian Cox
2004-06-30  9:30   ` Sven Luther
2004-06-30  9:40     ` Adrian Cox
2004-06-30  9:45       ` Sven Luther [this message]
2004-06-30 15:50   ` Sven Luther
2004-06-30 16:12     ` Adrian Cox
2004-06-30 16:23       ` Sven Luther
2004-06-30 16:39         ` Adrian Cox
2004-06-30 18:52           ` Sven Luther
2004-06-30 19:05             ` Adrian Cox
2004-06-30 19:38               ` Sven Luther
2004-07-01  7:59                 ` Geert Uytterhoeven
2004-07-01  8:42                   ` Adrian Cox
2004-07-01  8:48                     ` Geert Uytterhoeven
2004-07-01  8:57                     ` Sven Luther

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=20040630094546.GA24491@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=adrian@humboldt.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).