Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: buildroot@busybox.net
Subject: [Buildroot] question about /tftpboot
Date: Tue, 25 Mar 2008 18:31:48 +0100	[thread overview]
Message-ID: <47E93704.6070804@eclis.ch> (raw)
In-Reply-To: <00da01c88e8c$9254dd60$070514ac@atmel.com>

Ulf Samuelsson a ?crit :
>> 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.

Ok, thanks for the explanation.

My two proposed patches only take care of the point number 3 in your 
list. Currently there is two symbols used to copy some file into the 
tftpboot directory: BR2_LINUX_COPYTO and BR2_TARGET_ATMEL_COPYTO.


a) Each of this symbols cannot be set to anything other than "/tftpboot" 
because the scripts that use them have hard coded "/tftpboot" into them. 
  The 2 patches only fix for this simple problem. Without those patches 
the BR2_LINUX_COPYTO and BR2_TARGET_ATMEL_COPYTO are actually almost 
useless as modifying them are granted to fail because of the hard coded 
path in the scripts.

Take for example the "target/linux/Makefile.in.advanced" file. It 3 
lines with the path "/tftpboot" hard coded into it. My patch only 
replace those "/tftpboot" by the symbol "$(BR2_LINUX_COPYTO)". Same 
logic apply for the patch that replace the hard coded "/tftpboot" ba the 
symbol "$(BR2_TARGET_ATMEL_COPYTO)" into the files 
"target/device/Atmel/at91bootstrap/at91bootstrap.mk" and 
"target/device/Atmel/u-boot/u-boot.mk".

Did you see anything wrong that prevent those small patches to be applyed ?


b) Yes there is several symbols that are used to copy the linux kernel, 
but only the two symbols BR2_LINUX_COPYTO and BR2_TARGET_ATMEL_COPYTO 
are set by default to copy files into the /tftpboot directory. In my 
understanding there are both used for the exact same purpose: copy some 
files (not only the linux kernel) into the right tftpboot directory 
(possibly not alway "/tftpboot"). As there carry the same semantic, I 
wonder why we need two of them as there will alway have the same value 
to get a working setup. If there are alway the same, why not simply use 
one of them (BR2_LINUX_COPYTO) and replace the second 
(BR2_TARGET_ATMEL_COPYTO) by the first ?

Best Regards,
-- 
Jean-Christian de Rivaz

  reply	other threads:[~2008-03-25 17:31 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
2008-03-25 17:31         ` Jean-Christian de Rivaz [this message]
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=47E93704.6070804@eclis.ch \
    --to=jc@eclis.ch \
    --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