From: "Frédéric L. W. Meunier" <0@pervalidus.net>
To: Lionel Bouton <Lionel.Bouton@inet6.fr>
Cc: linux-kernel@vger.kernel.org
Subject: sis.patch.20020808 and 2.4.20 ?
Date: Fri, 22 Nov 2002 20:08:42 -0200 [thread overview]
Message-ID: <20021122220842.GE25050@pervalidus.net> (raw)
Any reason to not have sis.patch.20020808 in 2.4.20 ?
I have been using it with 2.4.19 in the last 3 months without any
noticeable problems.
Against 2.4.20-rc3 I get:
patching file drivers/ide/sis5513.c
patching file include/linux/pci_ids.h
Hunk #1 FAILED at 475.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/pci_ids.h.rej
There were no changes to sis5513.c. I can manually fix pci_ids.h.
BTW, what does
{ "SiS745", PCI_DEVICE_ID_SI_745, ATA_133, 0 },
"ATA_133" mean ?
I have an ASUS A7S333 and SiS745 is ATA100, like the SiS735
from my old K7S5A.
SIS5513: IDE controller on PCI bus 00 dev 15
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
SiS735 ATA 100 controller
SIS5513: IDE controller on PCI bus 00 dev 15
SIS5513: chipset revision 208
SIS5513: not 100% native mode: will probe irqs later
SiS745 ATA 100 controller
--
0@pervalidus.{net, {dyndns.}org}
reply other threads:[~2002-11-22 22:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021122220842.GE25050@pervalidus.net \
--to=0@pervalidus.net \
--cc=Lionel.Bouton@inet6.fr \
--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