Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "M. Grabert" <xam@cs.ucc.ie>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: 2.6.4-rc1-pa3 siimage/NS87415 IDE progess (and another mystery)!
Date: Sun, 11 Jul 2004 23:48:34 +0100	[thread overview]
Message-ID: <20040711224834.GA9503@sal.ucc.ie> (raw)
In-Reply-To: <20040711221829.GA27835@colo.lackof.org>

On Sun, Jul 11, 2004 at 04:18:29PM -0600, Grant Grundler wrote:

> [ Note the date! sorry...finally got around to this...]
>
> On Tue, Mar 09, 2004 at 03:26:00PM +0000, M. Grabert wrote:
> ...

No problem, as long as it's not forgotten ;)

> > But NOW I have some very weird problem for you!
> ...
> > Anyway, the IDE hard drive works with the onboard IDE controller of the C3000!
> > ... Well, not 100%. Let me explain. The mystery is:
> > 
> > IDE works fine (without DMA support, like in the 2.4 kernels), as long as
> > I interrupt the automatic boot up and to a "sea" followed by a "bo pri".
> 
> I looked at what the firmware is doing "out of the ordinary"
> and it's only writing three config space registers at 0x40-0x42 offset
> of the suckyio IDE. I appended a patch that does the same thing.
> Well, almost. We don't want to mask interrupts in CTRL2.

Great (investigative) work!

[...]

> Can you (or anyone else) test this patch with IDE disk drive on C3000?
> If this works, I can get rid of the magic numbers (define constants)
> and commit the code.

Will try it asap and post the result on the list.

Thanks alot,
   Max
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-07-11 22:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09  6:29 [parisc-linux] Results of (IDE) kernel tests with modified io.c M. Grabert
2004-03-09  6:36 ` Randolph Chung
2004-03-09  7:11   ` M. Grabert
2004-03-09  7:29     ` Randolph Chung
2004-03-09 15:26       ` [parisc-linux] 2.6.4-rc1-pa3 siimage/NS87415 IDE progess (and another mystery)! M. Grabert
2004-07-11 22:18         ` [parisc-linux] " Grant Grundler
2004-07-11 22:48           ` M. Grabert [this message]
2004-07-11 23:14           ` Randolph Chung
2004-07-11 23:34             ` Randolph Chung
2004-07-12  0:12               ` Grant Grundler
2004-07-12  3:37               ` M. Grabert
2004-07-12  4:19                 ` M. Grabert
2004-07-12 16:14                   ` Grant Grundler
2004-07-12 18:51                     ` M. Grabert
2004-07-13  3:56                       ` Grant Grundler
2004-07-13  5:59                         ` Grant Grundler
2004-07-12 19:44                     ` Alan Cox
2004-07-12 16:05                 ` Grant Grundler
2004-07-12 18:39                   ` M. Grabert
2004-07-12 18:50                     ` Randolph Chung
2004-07-13  4:17                     ` Grant Grundler
2004-07-11 23:34             ` Grant Grundler
2004-03-09 18:38       ` [parisc-linux] Results of (IDE) kernel tests with modified io.c Grant Grundler
2004-03-09 15:25     ` John David Anglin

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=20040711224834.GA9503@sal.ucc.ie \
    --to=xam@cs.ucc.ie \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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