I don't think your off topic, and I can help answer the first question.
A few people were wondering why the asic3 is used for MMC/SD when the
s3c2440 has a perfectly good controller already. The simple answer is that
the rx3715's camera is attached to the s3c2440's SDI controller. Why
wasn't the s3c2440's Camera interface used? I think it may have been
because the people who designed it already had WinCE software and for the
asic3 and HP's SDIO camera but none for the s3c2440's camera interface. Or
maybe it's because the camera interface needs a lot more tracks on the PCB
than the SDIO interface. These are only guesses.
I had a quick look at the G500 page and noticed you used the gcc
4.1.1Toolchain from Code sourcery. I compiled a kernel for the rx3715
with gcc
4.1.1 using the new ARM EABI and I saw the same problem you have seen with
init not starting. A bit of googling led me to this page.
http://wiki.debian.org/ArmEabiPort In smmary The ARM920T is an armv4t core
and there is some issue with this and the ARM EABI (function call return
instructions)... I think -mno-thumb-interwork option to GCC makes it work
but I haven't tested it. I'm using a gcc 3.4.4 glibc toolchain from
openembedded which maybe the same as the buildroot one you are using.
Sorry I can't help much with your second question. If the Eten is using the
Asic3 then have you tried it on different chip selects? A bit of looking in
Haret may help you find out more.
Rod.
On 9/16/06, Pierre Hébert <pierre-hebert_at_laposte.net> wrote:
>
> Hi,
>
> First I don't have an iPaq but an eten G500. It is based on a s3c2440, as
> the
> rx3715. So I am quite off topic but maybe someone can help me...
>
> My first question is perhaps a stupid question (sorry) : the h1930/h1940
> devices use the s3c2410mci driver for SD card access. As far as I can see
> this driver should also perfectly work with the s3c2440 (same registers,
> same
> logic, etc). But I noticed the rx3715 based on a s3c2440 don't use the
> s3c2410 driver, but the asic3 instead. As anybody an idea of why the
> rx3715
> does not use the builtin s3c2440 controller ?
>
> My second question is about the s3c2410mci driver in itself. I read a post
> on
> this mailing list
> http://www.handhelds.org/hypermail/rx3700-port/2/0202.html
> which deals with this driver. The last lines of the post shows the message
> log of the driver. It is exactly what I get on my device with the
> s3c2410mci
> driver, and this is because the driver does not receive interrupt request
> from the SD card module, the command request is blocked on
> a "wait_for_completion" call. So my question is : could it means that
> there
> is no hardware plugged on the s3c24xx MMC/SD/SDIO controller ? I checked
> the
> SDI command status register and it tells me the command has been sent (bit
> 11
> set).
> I made some tests with the asic3 driver but with no result.
>
> best regards,
>
> Pierre Hebert.
> _______________________________________________
> Rx3700-port mailing list
> Rx3700-port_at_handhelds.org
> https://www.handhelds.org/mailman/listinfo/rx3700-port
>
Received on Sat Sep 16 2006 - 09:11:37 EDT
This archive was generated by hypermail 2.2.0 : Sat Sep 16 2006 - 09:11:54 EDT