linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] IDE on CHRP LongTrail
Date: 24 Dec 2002 11:00:48 +0100	[thread overview]
Message-ID: <1040724049.559.2.camel@zion> (raw)
In-Reply-To: <Pine.GSO.4.21.0212241046170.1821-100000@vervain.sonytel.be>


On Tue, 2002-12-24 at 10:52, Geert Uytterhoeven wrote:
> On Tue, 24 Dec 2002, Geert Uytterhoeven wrote:
> > On 24 Dec 2002, Benjamin Herrenschmidt wrote:
> > > Regarding 2.4.21-pre2, did you check the linuxppc_2_4 tree ?
> >
> > Yes, I checked it during the weekend. Crash in IDE access operations.
> > I wrote down the addresses and the corresponding routine names. If you want
> > them, I can mail them (when I get back to the piece of paper).
>
> Thanks to my wife, here's the list:
>
> NIP C00A5908 ide_inb
> CR  C00A70F8 ide_config_drive_speed
> BT  C00A6F54 ide_config_drive_speed
>     C00A3314 config_for_pio
>     C00A356C sl82c105_ide_dma_off

Ok, I'll look at this when I'm back (I have no pci-ide HW at hand, and
ide-pmac works as it uses different MMIO access ops now).

Regarding briq and winbond, same answer, I need to check it out when I'm
back from vacation, I'm not yet sure about what OF does here, but I
surely want to switch it to fully native mode as well, especially since
the kernel will soon (I think 2.5 is already that way) ignore the BARs
completely when using legacy mode.

Ben.


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

  reply	other threads:[~2002-12-24 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 22:13 [PATCH] IDE on CHRP LongTrail Geert Uytterhoeven
2002-12-24  7:40 ` Benjamin Herrenschmidt
2002-12-24  9:09   ` Geert Uytterhoeven
2002-12-24  9:52     ` Geert Uytterhoeven
2002-12-24 10:00       ` Benjamin Herrenschmidt [this message]
2002-12-26 13:18     ` Geert Uytterhoeven
2002-12-26 16:17       ` Gabriel Paubert

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=1040724049.559.2.camel@zion \
    --to=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --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).