From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: "No such device" with PCI card
Date: Tue, 15 Jun 2004 12:38:59 +0200 [thread overview]
Message-ID: <20040615103859.GC20632@lug-owl.de> (raw)
In-Reply-To: <20040615102708.42219.qmail@web16604.mail.tpe.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
On Tue, 2004-06-15 18:27:08 +0800, jospehchan <jospehchan@yahoo.com.tw>
wrote in message <20040615102708.42219.qmail@web16604.mail.tpe.yahoo.com>:
> Hi Dominique,
> Thanks for your suggestion and help.
> I've tried my VIA VT6212L USB2.0 PCI card on other
> Linux system(x86 based) (RedHat 7.2 + kernel 2.4.16).
> And it works fine under kernel 2.4.16 with an USB
> patch from kernel 2.4.26.
> So I migrated the system to MIPS, but I was stuck by
> this problem.
> Altough I'm not familiar with device driver, but I
> will try Jan-Benedict's suggestion.
Before I get mixed up by pure confusion, let's put all the facts on the
table:
- What kind of MIPS system do you use *exactly*? What board? Which
kernel version? From where did you get your sources.
Some hint right here:
- If this isn't a very current 2.6.x CVS checkout from
linux-mips.org, you'd consider getting that. I won't recommend
anything else (possibly MVista has better ported kernels for
some specific boards?).
- A USB2.0 card is IMHO driven by the ehci driver, but I may be wrong.
I'm not exactly a regular USB user...
- Do you have output of "lspci", "lspci -v", "lspci -n", "lspci -vn" and
"lspci -nxxx" at your hand, once from your i386 test machine, once
from the MIPS board? Right, those commands mostly give the same
output, but each style eases reading for specific values:)
- Does your MOPS board have working on-board PCI devices? These don't
neccessarily have a PCI plug as you know them from add-on cards,
because they're directly built into the chipset. For instance, does
your board have onboard IDE interfaces?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-15 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 2:01 "No such device" with PCI card jospehchan
2004-06-15 9:02 ` Dominique Quatravaux
2004-06-15 10:27 ` jospehchan
2004-06-15 10:38 ` Jan-Benedict Glaw [this message]
2004-06-18 2:41 ` jospehchan
2004-06-18 6:19 ` Jan-Benedict Glaw
2004-06-18 17:05 ` Jun Sun
-- strict thread matches above, loose matches on Subject: below --
2004-06-14 11:56 jospehchan
2004-06-14 14:27 ` Jan-Benedict Glaw
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=20040615103859.GC20632@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.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