From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] support for CONFIG_SERIAL_TAG on ARM boards
Date: Thu, 19 May 2005 16:18:16 +0200 [thread overview]
Message-ID: <428CA028.2050904@imc-berlin.de> (raw)
Hi,
please consider this:
* Patch by Steven Scholz, 19 May 2005:
Add support for CONFIG_SERIAL_TAG on ARM baords
If someone wants to pass the board's serial number to the ARM linux kernel
using the ATAG_SERIAL mechanism, all she has to do is
#define CONFIG_REVISION_TAG
in the board config file and implement a trivial, board specific
#ifdef CONFIG_SERIAL_TAG
void get_board_serial(struct tag_serialnr *serialnr)
{
serialnr->low = (u32) sernum;
serialnr->high= (u32) 0;
}
#endif
Same goes for CONFIG_REVISION_TAG.
Thanks a million!
--
Steven Scholz
imc Measurement & Control
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: u-boot-serial_tag.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050519/34c54fe9/attachment.txt
next reply other threads:[~2005-05-19 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 14:18 Steven Scholz [this message]
2005-05-19 22:18 ` [U-Boot-Users] [PATCH] support for CONFIG_SERIAL_TAG on ARM boards 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=428CA028.2050904@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