linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: christos gentsis <christos_gentsis@yahoo.co.uk>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: linux-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Open hardware wireless cards
Date: Wed, 05 Jan 2005 22:19:27 +0000	[thread overview]
Message-ID: <41DC67EF.50105@yahoo.co.uk> (raw)
In-Reply-To: <20050105200526.GL5159@ruslug.rutgers.edu>

Luis R. Rodriguez wrote:

>On Wed, Jan 05, 2005 at 02:24:47PM -0500, Luis R. Rodriguez wrote:
><-- snip -->
>
>  
>
>>As far as support for the new chipsets goes -- sorry -- we won't be able
>>to support it as I don't think even Conexant has a final well tested
>>linux source base ready for 2.6. And even if we are given a source base
>>there is nothing we can do to get around the need for the closed-source 
>>softmac libs that it relies on. As much as I'd like to support it, I
>>don't want to get a headache to support something I cannot modify so I
>>won't be willing to support a half-opened driver as the atheros driver.
>>    
>>
>
>I'd also like to add...
>
>For those of you frustrated about our current wireless driver situation
>in open platforms --
>
>I think we probably will have this trouble with most modern hardware for a while
>(graphics cards, wireless driver, etc). A lot of has to do with patent
>infringement issues, "intellectual property" protection, and other
>business-oriented excuses.
>
>What I think we probably will have to do is just work torwards seeing if
>we can come up with our own open wireless hardware. I know there was
>a recent thread on lkml about an open video card -- anyone know where
>that ended up?
>
>If we can't come up with our own project to work on open hardware we can
>also just see if its feasible to purchase hardware companies on the
>verge of going backrupt and buy them out and release the specs/etc (a la
>blender). Can someone do the math here? I'm lazy.
>
>	Luis
>
>  
>
hello anyone

i thing that i didn't get the point... what did suppose to mean "we can 
come up with our own open wireless hardware". does it means that the 
kernel/ Linux community to design a complete hardware from scratch?

I'm don't know if there is people that would like to work in a project 
like that. if there is people that would like to do it i don't know if 
they can do it...

in case that i would had the choice then i get my wireless card, to make 
a new my one based to the design of someone that i don't know, not 
knowing if it is going to work in all cases and environments and knowing 
that i would use FPGA instead of ICs created for this functionality... i 
would not do it... i know what means designing hardware even if i don't 
have great experience in that (only some basic experience in Verilog...) 
i think that an idea like that is much closer to the opercores 
situation...(www.opencores.org)

According to my understanding, the problem with the wireless cards 
drivers and generally the drivers can be solved in two ways... first 
convincing the companies to produce the drivers or help other people 
code them.
OR
reverse engineering to the win drivers...(i think that this is harder)

i never understand way companies don't help with the drivers under 
linux.... in any way they are going to sell more products...

any way sorry for the long text and C.U. around.

Christos
 

  parent reply	other threads:[~2005-01-05 22:18 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
     [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 [this message]
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=41DC67EF.50105@yahoo.co.uk \
    --to=christos_gentsis@yahoo.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@studorgs.rutgers.edu \
    /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).