From: Norbert van Nobelen <norbert-kernel@edusupport.nl>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Open hardware wireless cards
Date: Thu, 6 Jan 2005 20:06:49 +0100 [thread overview]
Message-ID: <200501062006.49542.norbert-kernel@edusupport.nl> (raw)
In-Reply-To: <1105033349.15352.5.camel@krustophenia.net>
My personal opinion
Sound is mainly integrated on boards. Since developing a high end card is not
an easy job, and the market is pretty small for that (enough competition), I
think the wireless card is not too weird to do
Plus wireless is hot. What we can do is implement the standard and add a
little extra once we are done with that, linux a nice encryption layer for
linux to linux communication, thus giving linux (or a windowsbox with the
right drivers), a nice edge.
On Thursday 06 January 2005 18:42, you wrote:
> [removed prism-54 devel as it's subscribers only]
>
> On Thu, 2005-01-06 at 12:38 -0500, Luis R. Rodriguez wrote:
> > On Thu, Jan 06, 2005 at 12:37:15PM -0500, Lee Revell wrote:
> > > On Thu, 2005-01-06 at 12:24 -0500, Luis R. Rodriguez wrote:
> > > > On Thu, Jan 06, 2005 at 09:02:07AM +0100, Norbert van Nobelen wrote:
> > > > > You don't have to buy a company. There are white label
> > > > > manufacturers which are happy to produce any card you like
> > > >
> > > > Excellent
> > >
> > > Wireless?!? How abour a freaking pro audio interface (aka "sound
> > > card")? Wireless is like rocket science by comparison.
> >
> > So be it, let's shoot for friendly open sound card design manufacturing.
>
> It's been discussed on LAD and LAU. Not sure what current status is. I
> think if the open video card is viable then this certainly is. Pro
> sound gear is not a commodity market to the same extent that computer
> hardware is.
>
> Please check out those lists if you're interested, I don't want to start
> an OT thread here...
>
> Lee
--
<a href="http://www.edusupport.nl">EduSupport: Linux Desktop for schools and
small to medium business</a>
next prev parent reply other threads:[~2005-01-06 19:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050105192447.GJ5159@ruslug.rutgers.edu>
2005-01-05 20:05 ` Open hardware wireless cards Luis R. Rodriguez
2005-01-05 20:14 ` Lennart Sorensen
2005-01-05 20:48 ` linux-os
2005-01-05 21:35 ` Lennart Sorensen
2005-01-05 21:09 ` Tomasz Torcz
2005-01-08 20:47 ` Adrian Bunk
2005-01-09 9:59 ` Norbert van Nobelen
2005-01-09 22:28 ` Bernd Petrovitsch
2005-01-09 23:00 ` Alan Cox
2005-01-05 20:17 ` Raphael Jacquot
2005-01-05 20:26 ` Luis R. Rodriguez
2005-01-06 8:02 ` Norbert van Nobelen
2005-01-06 17:24 ` Luis R. Rodriguez
2005-01-06 17:37 ` Lee Revell
2005-01-06 17:38 ` Luis R. Rodriguez
2005-01-06 17:42 ` Lee Revell
2005-01-06 19:06 ` Norbert van Nobelen [this message]
[not found] ` <1105044024.15770.7.camel@krustophenia.net>
2005-01-06 20:51 ` Norbert van Nobelen
2005-01-06 17:59 ` Alan Cox
2005-01-06 20:25 ` Lee Revell
2005-01-07 10:37 ` Aaron Lehmann
2005-01-06 19:11 ` Raphael Jacquot
2005-01-06 19:32 ` Norbert van Nobelen
2005-01-06 21:00 ` Lee Revell
2005-01-06 21:24 ` Lennart Sorensen
2005-01-06 21:39 ` Jim Nelson
2005-01-06 21:42 ` Norbert van Nobelen
2005-01-08 11:58 ` Paul Jakma
2005-01-06 21:43 ` Christoph Hellwig
2005-01-05 20:22 ` [Prism54-users] " Steve Hill
2005-01-05 20:36 ` Luis R. Rodriguez
2005-01-05 22:19 ` christos gentsis
2005-04-19 19:07 ` Karel Kulhavy
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=200501062006.49542.norbert-kernel@edusupport.nl \
--to=norbert-kernel@edusupport.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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;
as well as URLs for NNTP newsgroup(s).