Keyspan USB serial adapter on Debian

[Steve DeLaney]

Hi All, not sure if this topic has been aired out before, but I'm new to the
forum.
I'm attempting to bring up a USB serial adapter on Debian so we can use a
serial port at 230.4KBaud
or faster if possible.

well I'd though to just plug my keyspan adapter in and away we go. not so
fast. Fedora, yes, Debian no.

From what I gather there were licensing objections in Debian leaving it to

the user to roll their own.
I'm trying to figure out if Keyspan support can just be built as a loadable
kernel module for Debian.
or is it more involved than that?

or another route we can go is find a different USB serial for Debian. since
we are targeting
230.4K that narrows the field. preliminary tests on Belkin were that it
topped out at 115K.

open to suggestions, recommendations..

TIA
/steverino2





-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
linux-usb-***@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

[Greg KH]

Post by Steve DeLaney
Hi All, not sure if this topic has been aired out before, but I'm new to the
forum.
I'm attempting to bring up a USB serial adapter on Debian so we can use a
serial port at 230.4KBaud
or faster if possible.
well I'd though to just plug my keyspan adapter in and away we go. not so
fast. Fedora, yes, Debian no.
From what I gather there were licensing objections in Debian leaving it to
the user to roll their own.
I'm trying to figure out if Keyspan support can just be built as a loadable
kernel module for Debian.
or is it more involved than that?

Try asking the Debian developers, this is not an upstream, kernel.org
issue, it is only due to Debian being very stubborn with regards to
their intrepretation of how firmware blobs work within the kernel and
the license of the kernel package.

Keyspan devices work very well with Linux on all other distros, so
perhaps you might just want to switch distros :)

good luck,

greg k-h

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
linux-usb-***@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

[maximilian attems]

Post by Greg KH

From what I gather there were licensing objections in Debian leaving it to
the user to roll their own.
I'm trying to figure out if Keyspan support can just be built as a loadable
kernel module for Debian.
or is it more involved than that?

Try asking the Debian developers, this is not an upstream, kernel.org
issue, it is only due to Debian being very stubborn with regards to
their intrepretation of how firmware blobs work within the kernel and
the license of the kernel package.
Keyspan devices work very well with Linux on all other distros, so
perhaps you might just want to switch distros :)
good luck,
greg k-h

gregkh the keyspan firmware restricts usage to boxes with keyspan,
so yes it is peculiar.
i'm in conversation with keyspan to fix that fact.

i'd be very happy to be able to renable it.
--
maks

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
linux-usb-***@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

[Alan Cox]

Post by maximilian attems
gregkh the keyspan firmware restricts usage to boxes with keyspan,
so yes it is peculiar.
i'm in conversation with keyspan to fix that fact.

The firmware blobs still want moving to the firmware request interface to
save resources and also to keep them seperate unless they provide them
GPLv2 with source.

Alan

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
linux-usb-***@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

[Greg KH]

Post by maximilian attems

Post by Greg KH

From what I gather there were licensing objections in Debian leaving it to
the user to roll their own.
I'm trying to figure out if Keyspan support can just be built as a loadable
kernel module for Debian.
or is it more involved than that?

Try asking the Debian developers, this is not an upstream, kernel.org
issue, it is only due to Debian being very stubborn with regards to
their intrepretation of how firmware blobs work within the kernel and
the license of the kernel package.
Keyspan devices work very well with Linux on all other distros, so
perhaps you might just want to switch distros :)
good luck,
greg k-h

gregkh the keyspan firmware restricts usage to boxes with keyspan,
so yes it is peculiar.

What do you mean it "restricts usage"? There is no problems with the
keyspan firmware being in the Linux kernel tree, except for the fact
that DEBIAN doesn't like it.

This is not a legal problem at all, but a made-up-one by some Debian
people only.

Post by maximilian attems
i'm in conversation with keyspan to fix that fact.

Fix what? Debian's odd rules? That would be interesting to see :)

Please don't bother the Keyspan people, this has nothing to do with
them, and everything to do with Debian.

Actually, when this first came up over 7 years ago, I posted a simple
way to fix this "issue" on the debian-legal mailing list. No one has
yet to send me a patch to do this, showing that no one really cares
about this issue, but that they just like arguing about it.

bleah,

greg k-h

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
linux-usb-***@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

[maximilian attems]

Post by Greg KH

Post by maximilian attems
gregkh the keyspan firmware restricts usage to boxes with keyspan,
so yes it is peculiar.

What do you mean it "restricts usage"? There is no problems with the
keyspan firmware being in the Linux kernel tree, except for the fact
that DEBIAN doesn't like it.
This is not a legal problem at all, but a made-up-one by some Debian
people only.

have you read the license?
"This firmware may not be modified and may only be used with
Keyspan hardware."

my box does not contain a keyspan hardware and it is infact
a quite bizarre clause to prevent hardware rip off.

Post by Greg KH

Post by maximilian attems
i'm in conversation with keyspan to fix that fact.

Fix what? Debian's odd rules? That would be interesting to see :)

fix the license, a bsd license like the qlogic stuff would do us a
great favour. i could just reenable keyspan.

Post by Greg KH
Actually, when this first came up over 7 years ago, I posted a simple
way to fix this "issue" on the debian-legal mailing list. No one has
yet to send me a patch to do this, showing that no one really cares
about this issue, but that they just like arguing about it.

i'm keeping away from d-legal and getting my job done.
so i'm still waiting for an applied or answer on the clarified dabusb
license patch.

i agree with ac that request_firmware() is the real goal,
as one should not need to recompile and reboot to update
the firmware.

if you can give a pointer to your d-legal post i'd be more then happy.
--
maks

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
linux-usb-***@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel