From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] AT91 Rework
Date: Thu, 05 Nov 2009 19:55:50 +0100 [thread overview]
Message-ID: <4AF31FB6.707@scharsoft.de> (raw)
In-Reply-To: <20091105170612.4932D3F6EC@gemini.denx.de>
Dear Wolfgang Denk,
>
> Umm... you are quite active for AT91 now - the position of the AT91
> is still orphaned; did you ever think about volunteering?
>
At the moment I'm work for different AT91 (AT91RM9200, AT91SAM9260 and
AT91SAM9360) in timeslot mode. But I am fully costumer driven, so that
it can be, i must switch to complette a other system like PIC and so on
or back to windows.
>
> I recomment to make this "u32" instead of "ulong".
>
I will replace this.
> again, please drop at least the parens and the casts.
It will be removed
Best regards,
Jens Scharsig
next prev parent reply other threads:[~2009-11-05 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 19:10 [U-Boot] AT91 Rework Jens Scharsig
2009-11-04 20:58 ` Jens Scharsig
2009-11-05 17:06 ` Wolfgang Denk
2009-11-05 18:55 ` Jens Scharsig [this message]
2009-11-05 20:12 ` Wolfgang Denk
2009-11-07 19:37 ` Jens Scharsig
2009-11-09 21:45 ` Wolfgang Denk
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=4AF31FB6.707@scharsoft.de \
--to=js_at_ng@scharsoft.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