From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Ben Schofield <b.w.schofield@durham.ac.uk>
Cc: linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: Toshiba IDE support: drivers/ide/pci/generic.c
Date: Tue, 24 Feb 2004 18:25:46 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.58L.0402241824050.23951@logos.cnet> (raw)
In-Reply-To: <401D7E16.5060203@durham.ac.uk>
On Sun, 1 Feb 2004, Ben Schofield wrote:
> Hi all,
>
> I've been having some problems with the IDE controller on my aged
> Portege 3440CT's port replicator, which I think I've now fixed, and I'd
> appreciate someone else's opinion before I submit a patch.
>
> The problem is that the controller reports itself with a vendor ID of
> 1179 (Toshiba) and a device ID of 0105 (unknown). In the 2.4.18 kernel,
> this was fine, since drivers/ide/ide-pci.c recognised it as an unknown
> IDE device and all was well.
>
> Somewhere between 2.4.18 and 2.4.22, the PCI IDE code seems to have been
> re-organised, and ide/generic.c seems not to have all the necessary code
> for unrecognised IDE devices. However, 1179:0103 is listed there as a
> Toshiba Piccolo controller, and adding 1179:0105 with the same data
> makes things work fine.
>
> Toshiba Piccolo support seems to have been removed entirely from
> generic.c in 2.6.2-rc3-bk1. This seems to have affected at least Jérôme
> Augé, who submitted a patch for a similar problem on 08/01 this year,
> containing
>
> #define PCI_DEVICE_ID_TOSHIBA_PICCOLO 0x0102
>
> So, I would guess that it's safe to assume at least 1179:0102, 1179:0103
> and 1179:0105 are Toshiba Piccolo controllers.
>
> Should I submit this as a patch?
Yes please.
> If I should, which kernel versions should I submit it against?
Ideally against 2.6 and 2.4.
prev parent reply other threads:[~2004-02-24 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 22:30 Ben Schofield
2004-02-24 21:25 ` Marcelo Tosatti [this message]
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=Pine.LNX.4.58L.0402241824050.23951@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=b.w.schofield@durham.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®