From: Tom Rini <trini@kernel.crashing.org>
To: linux-omap-open-source@linux.omap.com
Subject: OSK5912 and CF and network broken?
Date: Wed, 15 Mar 2006 11:30:06 -0700 [thread overview]
Message-ID: <20060315183006.GA16873@smtp.west.cox.net> (raw)
Hello. I'm trying to use current linux-omap-2.6 (source.mvista.com one)
git with the omap_osk_5912_defconfig and with U-Boot 1.1.4 release (+ 2
patches from this list). I can bring the board up just fine but when I
insert a CF device I see:
pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
NETDEV WATCHDOG: eth0: transmit timed out
...
NETDEV WATCHDOG: eth0: transmit timed out
pccard: card ejected from slot 0
Has anyone seen this before? Or should I just looking at the interrupt
routes? I'm assuming that the board does support me using both CF and
network at the same time. Thanks!
--
Tom Rini
http://gate.crashing.org/~trini/
next reply other threads:[~2006-03-15 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 18:30 Tom Rini [this message]
2006-03-15 18:36 ` OSK5912 and CF and network broken? Tony Lindgren
2006-03-15 19:22 ` Tom Rini
2006-03-15 19:41 ` Tony Lindgren
2006-03-15 20:31 ` Tom Rini
2006-03-16 17:03 ` Dirk Behme
2006-03-16 17:19 ` Tom Rini
2006-03-22 15:07 ` tony
2006-03-22 15:29 ` Dirk Behme
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=20060315183006.GA16873@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linux-omap-open-source@linux.omap.com \
/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