From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] question about /tftpboot
Date: Tue, 25 Mar 2008 16:12:06 +0100 [thread overview]
Message-ID: <00da01c88e8c$9254dd60$070514ac@atmel.com> (raw)
In-Reply-To: 47E8DBA5.3040304@eclis.ch
>>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found
>>> it broken by the target/linux/Makefile.in.advanced file and I proposed a
>>> patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
>>>
>>> Maybe the situation is better now.
> >
> >The linux kernel should possibly be copied several times, and
> >you cannot use a single symbol for this.
>
> Thanks Ulf for your hint, but did you have a more precise example ? I
> observed that only the Atmel targets uses a second symbol
> BR2_TARGET_ATMEL_COPYTO.
>
> I have updated my two proposed patchs
> http://bugs.uclibc.org/view.php?id=2384 and
> http://bugs.uclibc.org/view.php?id=2394 to match the current SVN head.
> There don't change the fact that there is two symbols, there only make
> the COPYTOP symbols possibly work if the tftpboot directory is anything
> other than "/tftpboot" like this is more and more the case on the new
> distributions.
>
> The idea to use only one symbol cam after I see that there is two of
> them for Atmel targets. I still don't see why something would go wrong
> if the BR2_TARGET_ATMEL_COPYTO will be replaced by the BR2_LINUX_COPYTO.
Not running Linux on my laptop at the moment, so I cannot check the svn
but as I see it, you want to be able to copy the linux image to
1) BINARIES_DIR
2) root file system (option)
3) A place where it is easy to download to the target using tftp,
which defaults to "/tftpboot".
It is OK, to make this programmable as long the default is used.
As an option, we could add a shell symbol "BUILDROOT_TFTP_DIR"
which overrides the menuconfig.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2008-03-25 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 17:40 [Buildroot] question about /tftpboot Habib Bouaziz-Viallet
2008-03-21 18:03 ` Jean-Christian de Rivaz
2008-03-21 18:16 ` Habib Bouaziz-Viallet
2008-03-21 19:42 ` Jean-Christian de Rivaz
2008-03-21 21:00 ` Jean-Christian de Rivaz
2008-03-21 21:20 ` Jean-Christian de Rivaz
2008-03-22 7:53 ` Habib Bouaziz-Viallet
2008-03-22 10:29 ` Habib Bouaziz-Viallet
2008-03-22 16:38 ` Jean-Christian de Rivaz
2008-03-22 16:54 ` Habib Bouaziz-Viallet
2008-03-22 17:36 ` Jean-Christian de Rivaz
2008-03-22 18:01 ` Habib Bouaziz-Viallet
2008-03-25 10:21 ` Ulf Samuelsson
2008-03-25 11:01 ` Jean-Christian de Rivaz
2008-03-25 15:12 ` Ulf Samuelsson [this message]
2008-03-25 17:31 ` Jean-Christian de Rivaz
2008-03-21 18:07 ` John Voltz
2008-03-21 18:20 ` Habib Bouaziz-Viallet
2008-03-21 18:33 ` JS
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='00da01c88e8c$9254dd60$070514ac@atmel.com' \
--to=ulf.samuelsson@atmel.com \
--cc=buildroot@busybox.net \
/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