From: "Mark W. Eichin" <eichin@thok.org>
To: linux-kernel@vger.kernel.org
Subject: CONFIG_BLK_DEV_SL82C105 should not be PPC/ARM specific
Date: Thu, 6 Sep 2001 18:30:01 -0400 (EDT) [thread overview]
Message-ID: <20010906223001.A63F613DC7@kuroneko> (raw)
[1.] One line summary of the problem:
CONFIG_BLK_DEV_SL82C105 should not be PPC/ARM specific
[2.] Full description of the problem/report:
kernel-source-2.4.9/drivers/ide/Config.in:
if [ "$CONFIG_PPC" = "y" -o "$CONFIG_ARM" = "y" ]; then
bool ' Winbond SL82c105 support' CONFIG_BLK_DEV_SL82C105
fi
The ALR Revolution 2XL dual-x86 (well, celeron) motherboard does, in
fact, use this controller:
00:02.0 IDE interface: Symphony Labs SL82c105 (rev 06) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at fcd0
and if I bludgeon the config so that it actually builds, it does work
(under 2.2, regrettably in pio-only mode, but I'll try 2.4.9 shortly)
W82C105: IDE controller on PCI bus 00 dev 10
W82C105: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfcd0-0xfcd7, BIOS settings: hda:pio, hdb:pio
SL82C105 command word: 5
IDE timing: 00001313, resetting to PIO0 timing
IDE control/status register: 08ff0801
[3.] Keywords (i.e., modules, networking, kernel):
kernel Config IDE block architecture x86
[4.] Kernel version (from /proc/version):
2.2.19, 2.4.9 (from inspection of source)
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
n/a
[6.] A small shell script or example program which triggers the
problem (if possible)
n/a
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
[7.2.] Processor information (from /proc/cpuinfo):
[7.3.] Module information (from /proc/modules):
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
[7.5.] PCI information ('lspci -vvv' as root)
00:02.0 IDE interface: Symphony Labs SL82c105 (rev 06) (prog-if 8a [Master SecP PriP])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 2 min, 40 max, 64 set, cache line size 08
Interrupt: pin A routed to IRQ 0
Region 4: I/O ports at fcd0
[7.6.] SCSI information (from /proc/scsi/scsi)
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
[X.] Other notes, patches, fixes, workarounds:
The hedrick IDE backport doesn't change this either.
_Mark_ <eichin@thok.org>
The Herd Of Kittens
next reply other threads:[~2001-09-06 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 22:30 Mark W. Eichin [this message]
2001-09-06 23:08 ` CONFIG_BLK_DEV_SL82C105 should not be PPC/ARM specific Russell King
2001-09-09 6:49 ` Mark Eichin
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=20010906223001.A63F613DC7@kuroneko \
--to=eichin@thok.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.