All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Standalone network calls
Date: Thu, 15 Mar 2007 19:03:35 +0100	[thread overview]
Message-ID: <45F98A77.1070505@semihalf.com> (raw)

Ben,

During the work to bring FreeBSD support in U-Boot we came accross a 
need for standalone network operations to send and receive an ethernet 
frame. In short, the approach is to have a native FreeBSD loader running 
on top of U-Boot as a standalone app. U-Boot's networking however, is 
pretty self-contained and, in particular, does not have a 'receive' 
primitive that would directly suit such purposes.

Please have a look at the attached patch and let me hear your comments 
about this direction in general and regarding these changes in 
particular. The included code actually works - we have a prototype 
FreeBSD loader running successfully on U-Boot extended in this fashion:

* eth_send() and eth_receive() are exported via the jump table and 
consumed by the FreeBSD loader

* the loader implements all TCP/IP and related protocols that it 
requires, so would be using U-Boot networking calls only as elementary 
send/receive

Beside the newly introduced eth_receive() one needs to export 
eth_{send,init,halt} too, and some other calls, but they can just be 
used without changes.

Any comments or suggestions welcome.

kind regards,
Rafal
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: u-boot-rcv.diff
Url: http://lists.denx.de/pipermail/u-boot/attachments/20070315/3a1691a7/attachment.txt 

             reply	other threads:[~2007-03-15 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 18:03 Rafal Jaworowski [this message]
2007-03-15 20:27 ` [U-Boot-Users] Standalone network calls Wolfgang Denk
2007-03-16 14:06 ` Ben Warren

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=45F98A77.1070505@semihalf.com \
    --to=raj@semihalf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.