Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Raspberry Pi build
Date: Sat, 18 Aug 2012 19:07:38 +0100	[thread overview]
Message-ID: <502FD9EA.6070009@gmail.com> (raw)
In-Reply-To: <CAA93jw4KTYEOMTJP7AX6DdNUTiQrT+Kw8tbDf4CuR4CVtSAPkA@mail.gmail.com>

On 18/08/12 18:38, Dave Taht wrote:
> 2) I have no idea what wireless chip is in the pi, nor its current state. (?)

The Raspberry Pi has no built-in wireless chip, but using USB WiFi 
adapters would be possible.
> 3) In order for things like fq_codel to have a hope of working well at
> the ethernet level, "Byte Queue Limits" (BQL) is *required*. I don't
> think any USB to ethernet adaptors have that yet, but I would welcome
> being wrong. And even if BQL worked over USB, we might have issues
> with the USB layer left to deal with... but BQL is easy to implement
> on native ethernet (6-8 lines of code or so)...
>
> I went looking through the source trees briefly and didn't find
> anything that jumped out at me. If you can point me to the right
> drivers I'll take a look. (and/or ask question 3 on a rasperry pi list
> for us?)
>

I did a bit of digging, and the Raspberry Pi uses the SMSC LAN9512 chip 
for wired Ethernet 
(http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf). The 
smsc95xx driver currently lacks BQL support, so that would need to be 
added first.

-- 
Robert Bradley

  reply	other threads:[~2012-08-18 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18  6:01 Mark Constable
2012-08-18 17:38 ` Dave Taht
2012-08-18 18:07   ` Robert Bradley [this message]
2012-08-18 18:53     ` Dave Taht
2012-08-19  0:59       ` Robert Bradley
2012-08-22 12:15         ` Mark Constable

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=502FD9EA.6070009@gmail.com \
    --to=robert.bradley1@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.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