From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Motorola i.MX support (1/2)
Date: Wed, 23 Jun 2004 10:41:39 +0200 [thread overview]
Message-ID: <40D94243.4000604@imc-berlin.de> (raw)
In-Reply-To: <40D67BC6.8040409@imc-berlin.de>
Steven Scholz wrote:
> Sascha Hauer wrote:
>
>> I've just had a look at the i.MX (MC9328 MX1, or however this thing is
>> called) Port in current CVS. The main differences are:
>>
>> - Like Robert said, my patch introduces less duplication of code
>> - the serial driver in CVS supports only a fixed (hardcoded) baudrate
>> - the architecture include file from cvs only has register definitions
>> while my port also has bitmasks for most registers as well as a
>> convenience function imx_gpio_mode which lets you set the gpio
>> primary/alternate functions without having to play with hex values.
>> - different boards supported. Two custom boards <-> MX1ADS. Adding
>> support for MX1ADS should be no problem, though, since we only have
>> to rewrite some register definitions. Unfortunately I don't
>> have the hardware.
>
>
> We will have one in the next few days. I'd love to help testing it.
I just got my brand new toy! :o)
So any news on the U-Boot i.MX support?
Steven
prev parent reply other threads:[~2004-06-23 8:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 11:57 [U-Boot-Users] [PATCH] Motorola i.MX support (1/2) Sascha Hauer
2004-06-18 11:20 ` Steven Scholz
2004-06-18 13:19 ` Wolfgang Denk
2004-06-18 14:23 ` Robert Schwebel
2004-06-18 15:02 ` Wolfgang Denk
2004-06-18 15:21 ` Robert Schwebel
2004-06-18 15:59 ` Wolfgang Denk
2004-06-18 19:30 ` Sascha Hauer
2004-06-19 8:21 ` Robert Schwebel
2004-06-19 11:05 ` Sascha Hauer
2004-06-21 6:13 ` Steven Scholz
2004-06-21 6:54 ` Wolfgang Denk
2004-06-21 6:57 ` llandre
2004-06-21 7:53 ` Robert Schwebel
2004-06-21 8:17 ` Steven Scholz
2004-06-21 8:52 ` Robert Schwebel
2004-06-21 6:10 ` Steven Scholz
2004-06-23 8:41 ` Steven Scholz [this message]
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=40D94243.4000604@imc-berlin.de \
--to=steven.scholz@imc-berlin.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