From: Zirong Wang <zirong.wang@ocegr.fr>
To: guinan@bluebutton.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MBX IDE
Date: Wed, 28 Jun 2000 17:46:16 +0200 [thread overview]
Message-ID: <395A1DC8.B5B13377@ocegr.fr> (raw)
In-Reply-To: Pine.LNX.4.21.0006280808460.16924-100000@gemini.home.net
Jamie Guinan wrote:
>
> There was a thread back in November about getting IDE going on
> an MBX,
>
> http://lists.linuxppc.org/listarcs/linuxppc-embedded/199911/msg00054.html
>
> Did anyone make any progress on this? Meaning, is there a recent
> kernel with working IDE-on-MBX. I know its an oddball combination,
> but I just wanted to check.
>
> With a few tweaks to MontaVista 2.2.13, I get as far as seeing,
>
> W82C105: IDE controller on PCI bus 00 dev 19
> W82C105: not 100% native mode: will probe irqs later
> SL82C105 command word: 5
> IDE timing: 00000909, resetting to PIO0 timing
> SL82C105 command word: 5
> IDE timing: 000003e4, resetting to PIO0 timing
>
I had a similar problem with a MTX board (not MBX), and the final
thing that deblocked the situation was by changing the file
/usr/src/linux/driver/block/sl82c105.c
I simply enabled the winbond by changing the line
pci_write_pci_config_dword(dev,0x40,0x10ff08a1) to
pci_write_pci_config_dword(dev,0x40,0x10ff0011)
I am not sure for your case since this line is enclosed between
"#ifndef CONFIG_MBX", maybe you can try put the line outside the
"ifdef" construct?
I had changed the 0x44 register's value to 0x0260:
pci_write_pci_config_dword(dev,0x44,0x0260)
hope this helps
---------------------------------------------------------------------
Zirong Wang Oce Industries 1, Rue J. Lemoine 94015 Creteil France
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-28 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 12:22 MBX IDE Jamie Guinan
2000-06-28 15:46 ` Zirong Wang [this message]
2000-06-29 7:56 ` Jamie Guinan
2000-06-29 8:45 ` Dan Malek
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=395A1DC8.B5B13377@ocegr.fr \
--to=zirong.wang@ocegr.fr \
--cc=guinan@bluebutton.com \
--cc=linuxppc-embedded@lists.linuxppc.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).