public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Question about smc911x driver (16/32 Bit support)
Date: Wed, 23 Apr 2008 08:37:16 +0200	[thread overview]
Message-ID: <480ED91C.4010400@tqs.de> (raw)
In-Reply-To: <f8328f7c0804221103i7af61e05h3134aea07eb95ee4@mail.gmail.com>

Hi Ben,

Ben Warren schrieb:
> Hi Jens,
> 
> On Tue, Apr 22, 2008 at 5:18 AM, Jens Gehrlein <sew_s@tqs.de> wrote:
>> Hi,
>>
>>  in the source code there is a preprocessor directive
>>  #error "SMC911X: Only 32-bit bus is supported".
>>
>>  We use a LAN9215i, which has a 16 Bit data interface only, connected to
>>  an i.MX31.
>>
>>  The LAN9215 is in the driver's ID list.
>>
>>  According to the data sheet accesses have to be 2x16 Bit to build the
>>  device's internal 32 Bit format.
>>
>>  What does this non-32-Bit exclusion exactly mean?
>>  Will the driver work on our HW configuration?
>>
> This #error message was included, because if you look at the code
> you'll see that the read/write accessors are 32-bit operations *(u32 *
> ).  These may or may not work on your configuration.  It should be
> trivial to write accessors for a 16-bit bus, but nobody had hardware
> to try it out on.  Please do so and submit a patch.

Yes, it seems, that we just need two additional functions which split a 
32 Bit access into two 16 Bit accesses. That should be easy. I'm going 
to create a patch as soon as I get the HW. But first I want to test 
whether the processor splits itself automatically.

Thank you very much.

Best Regards,
Jens

  reply	other threads:[~2008-04-23  6:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 12:18 [U-Boot-Users] Question about smc911x driver (16/32 Bit support) Jens Gehrlein
2008-04-22 18:03 ` Ben Warren
2008-04-23  6:37   ` Jens Gehrlein [this message]
2008-04-23 13:35     ` Magnus Lilja
2008-04-23 17:29       ` Ben Warren
2008-04-23 17:53         ` Magnus Lilja
2008-04-25 11:22           ` Jens Gehrlein

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=480ED91C.4010400@tqs.de \
    --to=sew_s@tqs.de \
    --cc=u-boot@lists.denx.de \
    /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