From: Pete Popov <ppopov@embeddedalley.com>
To: Ulrich Eckhardt <eckhardt@satorlaser.com>
Cc: linux-mips@linux-mips.org
Subject: Re: need help with CompactFlash/PCMCIA
Date: Wed, 16 Mar 2005 09:21:14 -0800 [thread overview]
Message-ID: <42386B0A.5070006@embeddedalley.com> (raw)
In-Reply-To: <200503161808.10088.eckhardt@satorlaser.com>
> OK, I'm just giving a short update on what I've found. In
> asm-mips/mach-generic/ide.h is a function ide_probe_legacy() which is called
> to determine IDE support but which returns 0 for my setup. I simply
> hard-wired this value to 1 and now at least it tries to probe something.
>
> However, it is looking at ioports in the range 366-3f6, which are already
> reserved by something else. Anyway, that is rather a legacy PC-style layout
> and thus probably doesn't apply to the PCMCIA version, if I'm not mistaken. I
> also tried simply removing the check whether they are reserved, but that just
> OOPSed.
>
> Looking at EBOOT (a bootloader for win CE that boots off the compactflash), it
> tries to access the IDE interface at address 0x1a00000 for io_addr and
> 0x1a00000e for control, let's see if I can find any IDE hardware at that
> address...
Uhm, I don't think you'll resolve this that easily. There is some code that
needs to go in the au1x00 socket driver which means you would have to
understand pretty well how this thing works. Ultimately the addresses you'll
probe are very high ioremapped addresses, since the pcmcia attribute, common
mem, and i/o are 36 bit physical addresses.
Pete
next prev parent reply other threads:[~2005-03-16 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 11:45 need help with CompactFlash/PCMCIA Ulrich Eckhardt
2005-03-15 17:31 ` Pete Popov
2005-03-16 5:51 ` Ulrich Eckhardt
2005-03-16 6:06 ` Pete Popov
2005-03-16 7:16 ` Ulrich Eckhardt
2005-03-16 8:02 ` Pete Popov
2005-03-16 17:08 ` Ulrich Eckhardt
2005-03-16 17:21 ` Pete Popov [this message]
2005-03-17 15:26 ` Ulrich Eckhardt
2005-03-18 4:13 ` Pete Popov
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=42386B0A.5070006@embeddedalley.com \
--to=ppopov@embeddedalley.com \
--cc=eckhardt@satorlaser.com \
--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