Re: firmware discussion
--000e0cd2c5d28d4deb048560d32d
Content-Type: text/plain; charset=UTF-8
i dont like this one at all:
Yet another would be to let users of devices that require
firmware that we can't distribute know that we're sorry for their plight
but they're on their own.
I agree with any of the others.
On Thu, Apr 29, 2010 at 05:12, Aggelos Economopoulos
<aoiko@cc.ece.ntua.gr>wrote:
> Joe Talbott wrote:
> > On Thu, Mar 04, 2010 at 08:46:47AM +0100, Sascha Wildner wrote:
> >> Am 03.03.2010 18:11, schrieb Joe Talbott:
> >>> My personal feeling is that we should do whatever
> >>> we can to make porting drivers as easy as possible.
> >> Port from where? We've not only ported drivers from FreeBSD in the past.
> >
> > My initial thought was to include both APIs though this would likely
> > lead to confusion.
>
> So, I was discussing the situation with firmware we can't redistribute
> legally. Getting the user to download it in, say, /etc/firmware would be
> easy enough, but apparently the freebsd firmware interface we've
> recently adopted to make the wireless sync easier assumes the firmware
> is contained in a module.
>
> This seems suboptimal to say the least. We don't want to have to build a
> module on the spot for each arbitrary file. One solution would be to
> have the kernel look into /etc/firmware at firmware_get() time
> (including some hack about the version number). Another would be to
> convert everything to use our old interface (straightforward, but some
> work). Yet another would be to let users of devices that require
> firmware that we can't distribute know that we're sorry for their plight
> but they're on their own.
>
> Which do we want to go with? Any other ideas?
>
> Aggelos
>
--
http://dfbsd.trackbsd.org.ar
--000e0cd2c5d28d4deb048560d32d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
i dont like this one at all:<br><br><blockquote class=3D"gmail_quote" style=
=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.=
8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-=
left-style: solid; padding-left: 1ex; ">
Yet another would be to let users of devices that require</blockquote><span=
class=3D"Apple-style-span" style=3D"font-family: arial, sans-serif; font-s=
ize: 13px; border-collapse: collapse; "><blockquote>firmware that we can=
9;t distribute know that we're sorry for their plight</blockquote>
<blockquote>but they're on their own.</blockquote></span><div><font cla=
ss=3D"Apple-style-span" face=3D"arial, sans-serif"><span class=3D"Apple-sty=
le-span" style=3D"border-collapse: collapse;"><br></span></font></div><div>=
<font class=3D"Apple-style-span" face=3D"arial, sans-serif"><span class=3D"=
Apple-style-span" style=3D"border-collapse: collapse;">I agree with any of =
the others.</span></font></div>
<div><font class=3D"Apple-style-span" face=3D"arial, sans-serif"><span clas=
s=3D"Apple-style-span" style=3D"border-collapse: collapse;"><br></span></fo=
nt><div><font class=3D"Apple-style-span" face=3D"arial, sans-serif"><span c=
lass=3D"Apple-style-span" style=3D"border-collapse: collapse;"><br>
</span></font><br><div class=3D"gmail_quote">On Thu, Apr 29, 2010 at 05:12,=
Aggelos Economopoulos <span dir=3D"ltr"><<a href=3D"mailto:aoiko@cc.ece=
..ntua.gr">aoiko@cc.ece.ntua.gr</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
<div><div></div><div class=3D"h5">Joe Talbott wrote:<br>
> On Thu, Mar 04, 2010 at 08:46:47AM +0100, Sascha Wildner wrote:<br>
>> Am 03.03.2010 18:11, schrieb Joe Talbott:<br>
>>> My personal feeling is that we should do whatever<br>
>>> we can to make porting drivers as easy as possible.<br>
>> Port from where? We've not only ported drivers from FreeBSD in=
the past.<br>
><br>
> My initial thought was to include both APIs though this would likely<b=
r>
> lead to confusion.<br>
<br>
</div></div>So, I was discussing the situation with firmware we can't r=
edistribute<br>
legally. Getting the user to download it in, say, /etc/firmware would be<br=
>
easy enough, but apparently the freebsd firmware interface we've<br>
recently adopted to make the wireless sync easier assumes the firmware<br>
is contained in a module.<br>
<br>
This seems suboptimal to say the least. We don't want to have to build =
a<br>
module on the spot for each arbitrary file. One solution would be to<br>
have the kernel look into /etc/firmware at firmware_get() time<br>
(including some hack about the version number). Another would be to<br>
convert everything to use our old interface (straightforward, but some<br>
work). Yet another would be to let users of devices that require<br>
firmware that we can't distribute know that we're sorry for their p=
light<br>
but they're on their own.<br>
<br>
Which do we want to go with? Any other ideas?<br>
<font color=3D"#888888"><br>
Aggelos<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br><a href=3D"http:=
//dfbsd.trackbsd.org.ar">http://dfbsd.trackbsd.org.ar</a><br>
</div></div>
--000e0cd2c5d28d4deb048560d32d--
討論串 (同標題文章)
完整討論串 (本文為第 10 之 17 篇)：