From: Steve Snyder <swsnyder@home.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: IDE chipset: CMD643 == CMD640?
Date: Wed, 13 Jun 2001 07:32:36 -0700 (PDT) [thread overview]
Message-ID: <0GEV00CTLHR5YP@mta3.snfc21.pbi.net> (raw)
My notebook, an old Pentium/150-based Dell Latitude, uses the CMD643
IDE controller. Is this effectively the same part as the CMD640 that
is warned about in the kernel doc? I'm trying to decide if the CMD640
bugfix is required in the v2.4.5 kernel options.
Thanks.
---------------------
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
CMD643: IDE controller on PCI bus 00 dev 40
CMD643: chipset revision 0
CMD643: not 100% native mode: will probe irqs later
CMD643: simplex device: DMA forced
ide0: BM-DMA at 0xfe00-0xfe07, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xfe08-0xfe0f, BIOS settings: hdc:pio, hdd:pio
---------------------
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: PicoPower Technology PT86C52x [Vesuvius] (rev 4).
Bus 0, device 6, function 0:
ISA bridge: PicoPower Technology PT80C524 [Nile] (rev 0).
Bus 0, device 7, function 0:
VGA compat controller: Neomagic NM2090 [MagicGraph 128V] (rev1).
Prefetchable 32 bit memory at 0x30000000 [0x303fffff].
Bus 0, device 8, function 0:
IDE interface: CMD Technology Inc PCI0643 (rev 0).
IRQ 14.
Master Capable. Latency=64. Min Gnt=2.Max Lat=4.
I/O at 0xfe00 [0xfe0f].
Bus 0, device 9, function 0:
CardBus bridge: Texas Instruments PCI1130 (rev 4).
Master Capable. Latency=168. Min Gnt=192.Max Lat=5.
Non-prefetchable 32 bit memory at 0x10000000 [0x10000fff].
Bus 0, device 9, function 1:
CardBus bridge: Texas Instruments PCI1130 (#2) (rev 4).
Master Capable. Latency=168. Min Gnt=192.Max Lat=5.
Non-prefetchable 32 bit memory at 0x10001000 [0x10001fff].
*** Steve Snyder ***
reply other threads:[~2001-06-13 14:36 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=0GEV00CTLHR5YP@mta3.snfc21.pbi.net \
--to=swsnyder@home.com \
--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;
as well as URLs for NNTP newsgroup(s).