From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Proposal for patch to configure networkparameters
Date: Sun, 22 Apr 2007 16:28:58 +0200 [thread overview]
Message-ID: <000901c784eb$0f3b8b50$01c4af0a@Glamdring> (raw)
In-Reply-To: 20070422135845.E3C70353428@atlas.denx.de
> I fail to see where there is a significant difference between the
> Linux kernel and U-Boot: you can patch either of the source trees to
> your liking, and when you copy a "$(LINUX26_DIR)/.config" file for
> Linux before running "make oldconfig" and "make uImage" you will copy
> a "include/configs/<board>.h" file with U-Boot before you run "make".
>
>
> The only difference, and I agree that it is a significant one, is
> that you cannot easily auto-generate "include/configs/<board>.h" from
> a Kconfig based configuration system. You would need at least some
> helper script, but even this should be straightforward to implement.
>
I consider it acceptable to have "include/configs/<board>.h" to be constant
for most users
of my S/W; but the networking environment will be different.
This is different for each user.
The memory configuration is also different.
>
> Instead of doing this, which fixes the problem for you while leaving
> the rest of the U-Boot community in the dark, we could also discuss
> if there is a way to make U-Boot configuration easier for all of us.
>
This is a major undertaking and a long term project, which I have no chance
of driving.
If someone decides that u-boot should be configured as part of the buildroot
configuration, then I can contribute.
Buildroot will allow me to create the contents of the board.h file in an
incremental fashion
if I let the automatically generated info override the board.h files. I
like that.
I do not need to test any boards that I do not have access to.
> It seems you prefer the first approach, while I am looking for the
> latter.
I am not sure I agree that I keep everyone in the dark since I publish the
source of my buildroot tree.
I would not have any problem providing this and my Atmel customized U-boot
to you for inclusion in your ftp site.
> Best regards,
>
> Wolfgang Denk
>
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
Technical support when I am not available:
AT89 C51 Applications Group: mailto:micro.hotline at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com Best AVR
next prev parent reply other threads:[~2007-04-22 14:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 19:22 [U-Boot-Users] Proposal for patch to configure network parameters Ulf Samuelsson
2007-04-20 20:40 ` Timur Tabi
2007-04-20 20:49 ` Wolfgang Denk
2007-04-20 20:55 ` Ben Warren
2007-04-20 21:51 ` [U-Boot-Users] Proposal for patch to configurenetwork parameters Ulf Samuelsson
2007-04-20 23:12 ` Wolfgang Denk
2007-04-20 23:39 ` Ulf Samuelsson
2007-04-21 0:31 ` Wolfgang Denk
2007-04-21 6:07 ` Ulf Samuelsson
2007-04-21 6:17 ` Ulf Samuelsson
2007-04-22 19:56 ` Timur Tabi
2007-04-22 20:25 ` Wolfgang Denk
2007-04-22 20:30 ` Timur Tabi
2007-04-22 21:27 ` Ulf Samuelsson
2007-04-20 21:59 ` [U-Boot-Users] Proposal for patch to configure network parameters Ulf Samuelsson
2007-04-20 23:14 ` Wolfgang Denk
2007-04-20 23:46 ` [U-Boot-Users] Proposal for patch to configure networkparameters Ulf Samuelsson
2007-04-20 20:47 ` [U-Boot-Users] Proposal for patch to configure network parameters Wolfgang Denk
2007-04-20 21:35 ` [U-Boot-Users] Proposal for patch to configure networkparameters Ulf Samuelsson
2007-04-20 22:59 ` Wolfgang Denk
2007-04-20 23:29 ` Ulf Samuelsson
2007-04-21 0:25 ` Wolfgang Denk
2007-04-21 6:05 ` Ulf Samuelsson
2007-04-21 10:37 ` Robert Schwebel
2007-04-22 5:30 ` Ulf Samuelsson
2007-04-22 7:27 ` Robert Schwebel
2007-04-22 8:45 ` Ulf Samuelsson
2007-04-22 11:05 ` Wolfgang Denk
2007-04-22 13:16 ` Ulf Samuelsson
2007-04-22 13:58 ` Wolfgang Denk
2007-04-22 14:28 ` Ulf Samuelsson [this message]
2007-04-22 18:48 ` Wolfgang Denk
2007-04-22 10:30 ` Wolfgang Denk
2007-04-20 23:03 ` [U-Boot-Users] Proposal for patch to configure network parameters Timur Tabi
2007-04-20 23:29 ` Wolfgang Denk
2007-04-20 23:58 ` [U-Boot-Users] Proposal for patch to configure networkparameters Ulf Samuelsson
2007-04-21 12:41 ` [U-Boot-Users] Proposal for patch to configure network parameters Andreas Schweigstill
2007-04-22 20:11 ` Timur Tabi
2007-04-22 20:31 ` Wolfgang Denk
2007-04-22 21:50 ` [U-Boot-Users] Proposal for patch to configure networkparameters Ulf Samuelsson
2007-04-22 23:57 ` Wolfgang Denk
2007-04-23 5:43 ` Ulf Samuelsson
2007-04-23 6:46 ` [U-Boot-Users] MPC8343 I2C problem Monstr at seznam.cz
2007-04-23 14:46 ` Timur Tabi
2007-04-23 7:00 ` [U-Boot-Users] MPC8343 NET without PHY Monstr at seznam.cz
2007-04-23 14:51 ` Timur Tabi
2007-04-23 8:59 ` [U-Boot-Users] Proposal for patch to configure networkparameters Wolfgang Denk
2007-04-23 9:24 ` Ulf Samuelsson
2007-04-23 10:50 ` Wolfgang Denk
2007-04-23 9:01 ` Ulf Samuelsson
2007-04-22 21:38 ` Ulf Samuelsson
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='000901c784eb$0f3b8b50$01c4af0a@Glamdring' \
--to=ulf@atmel.com \
--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