Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Habib Bouaziz-Viallet <habib.bouaziz@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] question about /tftpboot
Date: Sat, 22 Mar 2008 19:01:18 +0100	[thread overview]
Message-ID: <d449ded70803221101v4becc811uabfcb875fa6f50ca@mail.gmail.com> (raw)
In-Reply-To: <47E54380.6040101@eclis.ch>

2008/3/22, Jean-Christian de Rivaz <jc@eclis.ch>:
> Habib Bouaziz-Viallet a ?crit :
>  > 2008/3/22, Jean-Christian de Rivaz <jc@eclis.ch>:
>  >> Habib Bouaziz-Viallet a ?crit :
>  >>
>  >>
>  >>>>  > I am interested to know if it work for your case.
>  >>  > Oh it does not work for me ... unfortunately. I resolved the pb by a
>  >>  > symbolic link.
>  >>
>  >>
>  >> Ok. Can you give me the error message or the configuration to reproduce
>  >>  the problem ? I have some motivation to solve this issue.
>  > As i noticed in my previous post i make a symlink from /tftpboot -->
>  > /home/ ..../buildroot/tftpboot and build process works fine now
>  >
>  > habib at mizar:~/PROJETS/PERSO/buildroot$ ls tftpboot/
>  > at91sam9260dfc-dataflashcardboot-2.3.bin        autoscript.loopee!  vmlinux
>  > at91sam9260dfc-u-boot-1.2.0-atmel-20080322.bin  bzImage
>  >
>  > So what configuration would you see ? Is it my .config in buildroot root tree ?
>
>
> Initially yes, but finally no.
>
>  I see now that you use an Atmel target. Atmel target have an other
>  symbol used to copy file into the tftpboot directory. I suspect that the
>  patch you tryed only solve the tftpboot issue with the kernel, but not
>  the issue with the Atmel target. I really don't know the rational for
>  having two symbols for the tftpboot directory, this is maybe the result
>  of some historic of the Atmel targets. Anyone know ?
>
Yes my work is derived from Atmel AT91 Dev Kit but with a VGA
controller from EPSON. I read somewhere that buildroot allows us to
create own board support.

All are going smoothly for the moment (make menuconfig, make
busybox-menuconfig, make linux26-menuconfig ...etc.)


>  I was hoping that you used a target other than Atmel to see if my patch
>  was helpful. I am now back to the staring point. Sorry for having lost
>  some of your time.
>
>  Still, I will be very happy if some maintainers can give to me an guess
>  if the BR2_TARGET_ATMEL_COPYTO should be replaced by to BR2_LINUX_COPYTO
>  symbol. I am motivated to provide a appropriate patch to make the
>  tftpboot directory working correctly if it is not exactly "/tftpboot".
>
>  Have a good day,
>  --
>
> Jean-Christian de Rivaz
>


-- 
M. Bouaziz-Viallet

  reply	other threads:[~2008-03-22 18:01 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 [this message]
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
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=d449ded70803221101v4becc811uabfcb875fa6f50ca@mail.gmail.com \
    --to=habib.bouaziz@gmail.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