public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Justin Patrin <papercrane@gmail.com>
To: Norbert van Nobelen <norbert@edusupport.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compact Flash - simulating a card
Date: Wed, 24 Nov 2004 00:12:53 -0800	[thread overview]
Message-ID: <432beae0411240012519e976d@mail.gmail.com> (raw)
In-Reply-To: <200411240642.14660.Norbert@edusupport.nl>

On Wed, 24 Nov 2004 06:42:14 +0100, Norbert van Nobelen
<norbert@edusupport.nl> wrote:
> This is actually not really of topic, so so much for getting shunted.
> 
> Anyway:
> If you edit the modules part (manuals enough on the internet, watch your
> kernel version, because modules changed a bit between 2.4 and 2.6 kernels),
> you can force the identifier of your card to be matched with a CF device.
> Take the best matching device.
> If you don't have any match at all, you have a problem, i.e. it will not work.
> 

Well, it should be a storage device...

> I don't know the Zaurus (except from a nice picture), so I don't know what
> kind of port is used for the CF card (IDE? PCMCIA? other?). If it is an IDE
> port, it should work at once. It does not need any other information.

It's got a normal CF slot with (I think) a PCMCIA bridge. You can plug
in CF memory crad and microdrives as well as CF Wifi cards.

Basically I would want to connect the CF card as an IDE device (I have
no idea how to expose one device as another, although I think the
current CF storage device driver does this).

> 
> For the rest it sounds to me like you are doing a hardware hack.

So you think that I could force the kernel to assume that a device is
present? Meaning that there's no hardware-level stuff that has to
happen?

Of course the hard part is *where* I would edit the kernel for
this...probably in the PCMCIA stuff. I know that that's where the
timout message I was seeing was coming from.

> 
> Regards,
> 
> Norbert
> 
> 
> 
> On Tuesday 23 November 2004 22:34, Justin Patrin wrote:
> > I am not currently subscribed to this list as I figure I'll be shunted
> > to another anyway. Please CC me on replies to this thread. If I should
> > be asking "someone else" whether it be another list or group, let me
> > know.
> >
> > I currently have a Sharp Zaurus with OpenZaurus on it. I'm trying to
> > connect a device to the CF slot. Would is be possible to fake the CF
> > "startup"? I.e. connect a dumb device (which does not understand the
> > CF spec itself) but have the kernel able to pass certain requests on
> > to it? I have tried connecting the device and it sees it (as I've
> > hooked up the detection pins) but something times out. Sorry, I don't
> > have the exact message at the moment.
> 
> 

-- 
Justin Patrin

  reply	other threads:[~2004-11-24  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 21:34 Compact Flash - simulating a card Justin Patrin
2004-11-24  5:42 ` Norbert van Nobelen
2004-11-24  8:12   ` Justin Patrin [this message]
2004-11-24  9:08     ` Norbert van Nobelen

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=432beae0411240012519e976d@mail.gmail.com \
    --to=papercrane@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norbert@edusupport.nl \
    --cc=papercrane@reversefold.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