public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Any good __LOW COST__ MIPS SBC suggestion please
Date: Mon, 08 Mar 2010 07:18:29 -0500	[thread overview]
Message-ID: <4B94EB15.1030805@gmail.com> (raw)
In-Reply-To: <3b233f7d1003070926g46d4830dgae63fcefdb6f197c@mail.gmail.com>

Hi Balaji,

Please don't top quote.

Balaji Ravindran wrote:
> Hi Florian and Jerry,
> 
> Thanks for the inputs, i was actually going through the choices, and yea 
> as suggested Lemote seems to be a nice choice for me, and was wanting to 
> see distributors in the US / US shipping options.,

Based on your .in email domain, I did not expect that to be a problem. :-/

> also i had a look at the Linksys routers that you guys mentioned, but 
> one question, aren't the commercial products different from those of 
> development versions?, 

There are no development versions.  That is why they are cheap. ;-)

> I mean, when i opened up my WRT 610N, i could see  that, the main
> section of my router board is sealed in a steel casing(guess heat
> dissipater), though i can get the specs online,

The metal enclosure would be a EMI shield.  This is typically needed 
over the RF sections, sometimes needed over the processor sections.  It 
may or may not cover interesting things (processor, JTAG connector, etc).

> but does it have JTAG ports for debugging support? usually in production 
> versions, the odm's doesn't provide JTAG right? well, i couldn't see one 
> though.

The JTAG port is typically pads with no connector installed.  The 
designer/developers need it for development and the manufacturer 
typically needs it for loading new boards or debugging bad boards.

Developers get boards with connectors installed (special builds or 
add-on).  Manufacturers will use a fixture with "pogo pins" to stab the 
pads directly.  You get the opportunity for showing creativity, 
ingenuity, and soldering prowess.

> Just curious, will we be able to get development boards of Linksys WRT 
> SKUs? 

No.  Linksys is in the business of selling lots of turnkey boxes, not 
development stations.  Their attitude varies between tolerance and 
unhappiness with respect to hackers repurposing their boxes.

If you are looking for development boards, the "off-the-shelf" 
repurposing that Florian and I have mentioned do not fit your desires. 
You will need to restart your search with actual eval/dev boards and 
probably pay more money.  The advantage is that you will probably get 
better help and more information from the (re)seller.  The disadvantage 
is that you will pay more and probably learn less.

> Thanks
> 
> Balaji R

Best regards,
gvb

P.S. Florian: Thanks for the added info, that was very helpful.

[snip original]

  reply	other threads:[~2010-03-08 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06  4:30 [U-Boot] Any good __LOW COST__ MIPS SBC suggestion please Balaji Ravindran
2010-03-06 20:42 ` Jerry Van Baren
2010-03-07 10:50   ` Florian Fainelli
2010-03-07 17:26     ` Balaji Ravindran
2010-03-08 12:18       ` Jerry Van Baren [this message]
2010-03-10  1:44 ` Damien Dusha

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=4B94EB15.1030805@gmail.com \
    --to=gvb.uboot@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