public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OSK5912 and CF and network broken?
Date: Wed, 22 Mar 2006 07:07:28 -0800	[thread overview]
Message-ID: <20060322150725.GA5748@atomide.com> (raw)
In-Reply-To: <20060316171940.GE16873@smtp.west.cox.net>

* Tom Rini <trini@kernel.crashing.org> [060316 09:20]:
> On Thu, Mar 16, 2006 at 06:03:02PM +0100, Dirk Behme wrote:
> > Tom Rini wrote:
> > >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!
> > 
> > Yes, board supports both, CF and network. However, OSK CF 
> > hardware is limited and is really troublesome.
> 
> I wonder if my board is just more troublesome than most.  If I turned off
> network (and used a ramdisk for userspace) I then got to the point of:
> 
> pccard: PCMCIA card inserted into slot 0                                      
> pcmcia: registering new device pcmcia0.0                                        
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> hdb: probing with STATUS(0x00) instead of ALTSTATUS(0x51)                       
> ide-cs: ide_register() at 0xc2852000 & 0xc285200e, irq 222 failed
> 
> with an old 16MB CF card.  With my 2.2GB microdrive I get more of the
> messages, but the same result.  FWIW, u-boot won't load if the MD is
> inserted, but will if the CF is.
> 
> But perhaps I need a better cardmgr options file?  I don't have anything
> board-specific in mine.  Thanks!

I believe there may be some different timings needed depending on the
OSK revision.

Tony

  reply	other threads:[~2006-03-22 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 18:30 OSK5912 and CF and network broken? Tom Rini
2006-03-15 18:36 ` 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 [this message]
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=20060322150725.GA5748@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=trini@kernel.crashing.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