Lee Mathers ha scritto:
Now we have hardware ASIC that depend on the most part a (dll in
windows) or .ko .o file under linux to provide the entire instruction
set. Think Winmodems, Winprinters etc
Well, winmodem case is the only I could *almost* understand
closed-source drivers: the
David Newall ha scritto:
Precisely: One purpose of the driver is to enforce local compliance.
It can't *enforce* it anyway, at least if the users are all around the
world.
Yes it can. You're confusing the software with different or modified
software. Different things. And by the way, if
David Newall ha scritto:
Precisely: One purpose of the driver is to enforce local compliance.
It can't *enforce* it anyway, at least if the users are all around the
world.
Yes it can. You're confusing the software with different or modified
software. Different things. And by the way, if
Lee Mathers ha scritto:
Now we have hardware ASIC that depend on the most part a (dll in
windows) or .ko .o file under linux to provide the entire instruction
set. Think Winmodems, Winprinters etc
Well, winmodem case is the only I could *almost* understand
closed-source drivers: the
David Newall ha scritto:
That's naive, since requirements differ in different jurisdictions, as
I'm sure you are perfectly aware.
Naive? Who thinks a limit can be enforced by sw is naive!
He's missing a little detail: Internet. :-)
Precisely: One purpose of the driver is to enforce local
David Newall ha scritto:
"Of course", because in many parts of the world, a device who's
manufacturer fails to take reasonable steps to prevent it from being
used outside regulatory limits is illegal. Providing source code not
only is a failure to take those reasonable steps, but is quite
Christer Weinigel ha scritto:
I think it is perfectly within their rights to do so. I think it's
kind of silly to try to hide it, if someone wants to boost the maximum
transmit power, they're going to hack the firmware anyway. But if it
makes Intel happy, well... :-)
And break the HW :-)
Christer Weinigel ha scritto:
I think it is perfectly within their rights to do so. I think it's
kind of silly to try to hide it, if someone wants to boost the maximum
transmit power, they're going to hack the firmware anyway. But if it
makes Intel happy, well... :-)
And break the HW :-)
David Newall ha scritto:
Of course, because in many parts of the world, a device who's
manufacturer fails to take reasonable steps to prevent it from being
used outside regulatory limits is illegal. Providing source code not
only is a failure to take those reasonable steps, but is quite the
David Newall ha scritto:
That's naive, since requirements differ in different jurisdictions, as
I'm sure you are perfectly aware.
Naive? Who thinks a limit can be enforced by sw is naive!
He's missing a little detail: Internet. :-)
Precisely: One purpose of the driver is to enforce local
Christer Weinigel ha scritto:
It isn't that easy. The "Tamper-Proof Torx" screws on a vacuum cleaner
or a toaster won't stop anybody from opening up the thing, I mean every
little hardware store stocks those Torx bits. But by using a slightly
odd screw, the company can say "look, we'we done
David Newall ha scritto:
This does, of course,
disadvantage Linux with respect to many classes of devices, for example
GSM transceivers when used in those parts of the world^ where regulatory
requirements prohibit modification of power or frequency settings, which
effectively prohibits
David Newall ha scritto:
This does, of course,
disadvantage Linux with respect to many classes of devices, for example
GSM transceivers when used in those parts of the world^ where regulatory
requirements prohibit modification of power or frequency settings, which
effectively prohibits
Christer Weinigel ha scritto:
It isn't that easy. The Tamper-Proof Torx screws on a vacuum cleaner
or a toaster won't stop anybody from opening up the thing, I mean every
little hardware store stocks those Torx bits. But by using a slightly
odd screw, the company can say look, we'we done
Jiri Kosina ha scritto:
>> My USB mouse recently started giving me phantom scrolls (movements of
>> the mouse wheel, even I made sure the wheel was in a resting position)
>> in recently kernels. It happened too infrequently for me to care.
> Did this also start in 2.6.24, as in Mark's case?
It
Jiri Kosina ha scritto:
My USB mouse recently started giving me phantom scrolls (movements of
the mouse wheel, even I made sure the wheel was in a resting position)
in recently kernels. It happened too infrequently for me to care.
Did this also start in 2.6.24, as in Mark's case?
It
Paul Fulghum ha scritto:
> There is no one policy here that will make everyone happy.
> Some will want all the data before some was lost,
> others the data after some was lost.
IMVHO the only sane thing is ALWAYS avoid "holes" (some old data, then
the "hole" of lost data, then some new data) after
Paul Fulghum ha scritto:
There is no one policy here that will make everyone happy.
Some will want all the data before some was lost,
others the data after some was lost.
IMVHO the only sane thing is ALWAYS avoid holes (some old data, then
the hole of lost data, then some new data) after a
18 matches
Mail list logo
