All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] pata_hpt3x3: Major reworking and testing
Date: Tue, 3 Jul 2007 22:12:01 +0200	[thread overview]
Message-ID: <200707032212.01619.bzolnier@gmail.com> (raw)
In-Reply-To: <20070703185652.0b807fcc@the-village.bc.nu>

On Tuesday 03 July 2007, Alan Cox wrote:
> > The new improved driver is not really better than the old one because
> > the old one is broken. :)
> > 
> > Old driver does identical configuration when it comes to PIO modes.
> 
> No the old driver doesn't even do that. It starts up. It spuriously
> adjusts some non writable PCI BAR registers, prints a message about
> resources being in use already then exits.

OK, thanks for clarifying this.

> I had a poke around the setup. As far as I can observe we break even if
> the ROM timing values are used as is. I suspect documentation or a good
> deal of luck is needed.

Yeah.

BTW the original Andre's driver had some references to misc configuration
registers at offsets 0x10 and 0x11 of PCI BAR4.

http://www.linuxhq.com/kernel/v2.3/10/drivers/block/hpt343.c

Does anybody have DOS driver for HPT343?  Google doesn't have it...

Thanks,
Bart

  reply	other threads:[~2007-07-03 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 15:10 [PATCH] pata_hpt3x3: Major reworking and testing Alan Cox
2007-07-03 15:40 ` Jeff Garzik
2007-07-03 15:49   ` Alan Cox
2007-07-03 17:38 ` Bartlomiej Zolnierkiewicz
2007-07-03 17:56   ` Alan Cox
2007-07-03 20:12     ` Bartlomiej Zolnierkiewicz [this message]
2007-07-03 20:41       ` Sergei Shtylyov
2007-07-03 22:44         ` Bartlomiej Zolnierkiewicz
2007-07-04 14:28           ` Sergei Shtylyov

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=200707032212.01619.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.