From: "Franz Böhm" <fboehm@aon.at>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] sysfs compat
Date: Tue, 04 May 2010 14:36:28 +0200 [thread overview]
Message-ID: <4BE014CC.50904@aon.at> (raw)
In-Reply-To: <201005041340.07717.onelektra@gmx.net>
Hi Elektra,
the problem lies somewhere else like mentioned earlier:
" ... Using open source drivers instead is not always an opinion because
it's very hard to comply with radio regulations and get your product
certified. ..."
You are right regarding the quality of binary drivers from chip
suppliers. But if you pay lots of money for an SDK with outdated kernel
:-) and with binary drivers included, the supplier should give you
support for every problem their binary drivers create.
For example you will never ever get 100% source from Sigma Designs to
debug their binary stuff because they mostly fear loosing their
intellectual property.
Of course it's a different point of view if you are working on a
commercial product or on a software project for some sort of community.
In the first way you have to get your product certified. In the second
way you want to prevent using binary drivers.
Regards,
Franz
elektra schrieb:
> Hello Franz -
>
> as a comment: Whenever I used drivers from a chip manufacturer so far I had a
> miserable experience. Basic features and most common applications usually
> work, but thats it. Drivers are usually buggy and unmaintained. Particularly
> ad-hoc mode support usually is theoretically there but practically broken. I
> know of no proprietary vendor driver that works properly.
>
> The fact that you are usually bound to a very old version of Linux is telling.
> I only use / promote chips with decent open-source support. OpenWrt is
> awesome.
>
> Cheers,
> Elektra
>
next prev parent reply other threads:[~2010-05-04 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 0:28 [B.A.T.M.A.N.] sysfs compat Marek Lindner
2010-05-03 0:28 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: adding MAC_FMT compatibility Marek Lindner
2010-05-03 0:28 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: adding sysfs compat Marek Lindner
2010-05-03 8:03 ` [B.A.T.M.A.N.] " Andrew Lunn
2010-05-03 9:05 ` Franz Böhm
2010-05-03 10:30 ` Sven Eckelmann
2010-05-03 20:40 ` Simon Wunderlich
2010-05-04 2:21 ` Marek Lindner
2010-05-04 11:13 ` Franz Böhm
2010-05-04 11:40 ` elektra
2010-05-04 12:36 ` Franz Böhm [this message]
2010-05-04 13:05 ` elektra
2010-05-04 17:34 ` Franz Böhm
2010-05-04 23:59 ` RHS Linux User
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=4BE014CC.50904@aon.at \
--to=fboehm@aon.at \
--cc=b.a.t.m.a.n@lists.open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox