From: maggi9999 <maggi9999@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Adding a new file transfer protocol to Uboot
Date: Sun, 2 May 2010 23:09:17 -0700 (PDT) [thread overview]
Message-ID: <28431798.post@talk.nabble.com> (raw)
In-Reply-To: <h2uf8328f7c1004270658meed666e0n7012d26c7881a16c@mail.gmail.com>
Ben Warren-2 wrote:
>
> Hello Maggi9999,
>
> On Tue, Apr 27, 2010 at 6:27 AM, maggi9999 <maggi9999@gmail.com> wrote:
>
>>
>> hi all,
>>
>> i'm very new to uboot.i would like to add new file transfer protocol like
>> tftp. Server sends the file as chunks and uboot has to receive and
>> reconstruct it.for that in uboot can i add the new protocol in /net
>> folder
>> or is there any folder in uboot which can hold it?Is adding new protocol
>> will come to gpl?
>>
>
> Anything you wish to submit will be considered. If your protocol has
> advantages over the existing TFTP and NFS implementations, please explain
> what's better. Of course, the protocol needs to be completely open and
> documented on both client and server sides. You must provide a CONFIG
> option so that users opt in to using the protocol, and doesn't add to
> image
> size if they don't. You are correct that /net is the correct place.
>
> regards,
> Ben
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
thank you very much for your reply.
--
View this message in context: http://old.nabble.com/Adding-a-new-file-transfer-protocol-to-Uboot-tp28376949p28431798.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-05-03 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 13:27 [U-Boot] Adding a new file transfer protocol to Uboot maggi9999
2010-04-27 13:58 ` Ben Warren
2010-05-03 6:09 ` maggi9999 [this message]
2010-04-27 20:37 ` 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=28431798.post@talk.nabble.com \
--to=maggi9999@gmail.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