From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Dave Platt <dplatt@radagast.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: Linux Packet Interface Hardware
Date: Thu, 17 Jun 2010 01:49:16 +0300 [thread overview]
Message-ID: <20100616224916.GP898@mea-ext.zmailer.org> (raw)
In-Reply-To: <4C195062.7050401@radagast.org>
On Wed, Jun 16, 2010 at 03:29:54PM -0700, Dave Platt wrote:
...
> > Thanks all for the ideas/input. I think the BPQether driver best fits
> > what I was hoping to find, except for the fact that it doesn't exist
> > off-the-shelf yet....
>
> I agree - an interesting idea.
...
> The Cypress microcontrollers with the EZ-USB stack could be
> suitable targets. These have the ability to have their firmware
> downloaded by the host over USB each time they plug in and
> enumerate... easy updating, no need to burn EEPROMs or flash
> firmware directly into the chips. High-end PIC micros could
> be another workable choice.
While the idea of "load the firmware at boot" is great idea during
development, it becomes not-so-great in deployment.
I would prefer flashing in the production firmware, and possibly
supplying a way to re-flash it if necessary, but never playing
development mode games with users.
Even with windows we are seeing that 2-3 years down the road the
old drivers / firmware loads become non-functional when windows
versions change. It is always better to use abstractions that
do not need any sort of device driver disks on any platform, and
the way to achieve that is preferrably not subscribing on OS vendors
driver integration program.
What if your modem has ethernet? No way to upload firmware thru
USB then. (BPQether over ethernet...)
73 de Matti, OH2MQK
next prev parent reply other threads:[~2010-06-16 22:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 23:43 Linux Packet Interface Hardware Jim Kusznir
2010-06-16 1:19 ` Ray Wells
2010-06-16 1:24 ` Matti Aarnio
2011-02-15 18:36 ` Jim Kusznir
2010-06-16 2:05 ` Dave Platt
2010-06-16 12:45 ` Curt, WE7U
2010-06-16 16:16 ` Jim Kusznir
2010-06-16 16:46 ` Curt, WE7U
2010-06-16 23:25 ` Jim Kusznir
2010-06-17 12:49 ` Curt, WE7U
2010-06-21 6:17 ` walter harms
2010-06-16 22:29 ` Matti Aarnio
2010-06-16 23:53 ` Dave Platt
2010-06-16 22:29 ` Dave Platt
2010-06-16 22:49 ` Matti Aarnio [this message]
2010-06-16 23:33 ` Curt, WE7U
2010-06-17 0:02 ` Dave Platt
-- strict thread matches above, loose matches on Subject: below --
2010-06-17 2:24 Andrew Errington
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=20100616224916.GP898@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=dplatt@radagast.org \
--cc=linux-hams@vger.kernel.org \
/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.