[Kernel-packages] [Bug 1295409] Re: WiMAX to ubuntu-drivers-common or uspkg for x86/_64?
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295409 Title: WiMAX to ubuntu-drivers-common or uspkg for x86/_64? Status in “linux” package in Ubuntu: Confirmed Bug description: I noticed that Sprint's deal with Clear is starting to wrap up in 2015. Clear stopped accepting new customers Sept 2013. In June of 2013, Sprint started to offer free LTE replacement devices without a contract extension or renewal. FreedomPop states their WiMAX service (MVNO) to be only available until 2015. I have never seen a WiMAX USB or mini-PCIe device that doesn't also have 3G,WiFi, or LTE also other than the U1901. From what I can see, Sprint isn't even selling new WiMAX devices anymore, nor are any of the standalone MVNOs. Most current WiMAX chips are on standalone ARM devices and ARM Android phones. Samsung's WiFi offerings are supported through userspace drivers in the madwimax package. bcm_wimax.ko is still in staging, with tons of other firmware and cruft collecting elsewhere. Most WiMAX related bugs still exist in the kernel and the ubuntu fs. Most if not all single-mode 4G devices aren't being updated (drivers or firmware) with many companies for most models declaring EOL or doing so unofficially; including Huawei, Intel. and Sierra Wireless. Outside of the USA almost all the networks are on dual mode 4G even (WiMAX/Advanced + LTE) and are mostly router/hotspot based. The lone example of WiMAX only use in any sort of mass produced miniPCIe or USB consumer device currently, is in Samsung Chromebook (In Malaysia) which is ARM powered. This should all be moved elsewhere imho, as WiMAX drivers as a kernel default =y makes little sense on x86/_64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1295409] Re: WiMAX to ubuntu-drivers-common or uspkg for x86/_64?
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1295409 Title: WiMAX to ubuntu-drivers-common or uspkg for x86/_64? Status in “linux” package in Ubuntu: Confirmed Bug description: I noticed that Sprint's deal with Clear is starting to wrap up in 2015. Clear stopped accepting new customers Sept 2013. In June of 2013, Sprint started to offer free LTE replacement devices without a contract extension or renewal. FreedomPop states their WiMAX service (MVNO) to be only available until 2015. I have never seen a WiMAX USB or mini-PCIe device that doesn't also have 3G,WiFi, or LTE also other than the U1901. From what I can see, Sprint isn't even selling new WiMAX devices anymore, nor are any of the standalone MVNOs. Most current WiMAX chips are on standalone ARM devices and ARM Android phones. Samsung's WiFi offerings are supported through userspace drivers in the madwimax package. bcm_wimax.ko is still in staging, with tons of other firmware and cruft collecting elsewhere. Most WiMAX related bugs still exist in the kernel and the ubuntu fs. Most if not all single-mode 4G devices aren't being updated (drivers or firmware) with many companies for most models declaring EOL or doing so unofficially; including Huawei, Intel. and Sierra Wireless. Outside of the USA almost all the networks are on dual mode 4G even (WiMAX/Advanced + LTE) and are mostly router/hotspot based. The lone example of WiMAX only use in any sort of mass produced miniPCIe or USB consumer device currently, is in Samsung Chromebook (In Malaysia) which is ARM powered. This should all be moved elsewhere imho, as WiMAX drivers as a kernel default =y makes little sense on x86/_64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
