[opensuse-kernel] Advise for Leap kernel with patches (Support for Intel Compute Stick)
Hi, I'm looking for advise to ensure a good and long life to this kind of hardware. http://www.intel.com/content/www/us/en/compute-stick/intel-compute-stick.htm... I've took the stck1a32wfc (windows preloaded) due to better hardware. The only thing that doesn't work out of the box is the Realtek wifi/bluetooth chipset. a rtl8723bs Fortunately there's one person that have good sources. https://github.com/hadess/rtl8723bs So after installing Leap from usb key, and prepare the environment I've tested first the build install of the drivers without any kernel-patches. Connect but fail to handle network load etc... hadess has some patches for kernel < 4.3 So good so far, I've patched the kernel and rebuild the whole (On the stick just for a try and science 320 minutes) Once this patched 4.1.12 + the driver everything work now. I've a perfect kodi (new xmbc name) connected on the tv. I'm looking for your input on several points : - Will the driver code end up in kernel one day? - What would be best way to maintain a derivative kernel on which I can add the needed patches ? - I'm okay to build a kmp- on obs, do you see any kind of problem? (mostly license) At the end, I would like to get a easy as (zypper/kiwi) build to create a dedicated susestudio/kiwi build for this model so we could have something easy to install for grand-aunty ;-) Thanks for your remarks, ideas, flame whatever. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Sun, 22 Nov 2015 18:05:27 +0100, Bruno Friedmann wrote:
Hi, I'm looking for advise to ensure a good and long life to this kind of hardware.
http://www.intel.com/content/www/us/en/compute-stick/intel-compute-stick.htm...
I've took the stck1a32wfc (windows preloaded) due to better hardware.
The only thing that doesn't work out of the box is the Realtek wifi/bluetooth chipset.
a rtl8723bs
Fortunately there's one person that have good sources. https://github.com/hadess/rtl8723bs
So after installing Leap from usb key, and prepare the environment I've tested first the build install of the drivers without any kernel-patches. Connect but fail to handle network load etc...
hadess has some patches for kernel < 4.3 So good so far, I've patched the kernel and rebuild the whole (On the stick just for a try and science 320 minutes)
Once this patched 4.1.12 + the driver everything work now.
I've a perfect kodi (new xmbc name) connected on the tv.
I'm looking for your input on several points :
- Will the driver code end up in kernel one day?
To which kernel? openSUSE or upstream? Basically openSUSE kernel takes only changes from upstream, so it should be merged to upstream at first. Many Realtek drivers go via staging tree, so a fast way would be to ask the driver author to submit the driver patches to staging tree.
- What would be best way to maintain a derivative kernel on which I can add the needed patches ?
I don't think you need to patch the kernel itself to build the driver. Usually a driver can be built as an external module. For openSUSE, it's a KMP.
- I'm okay to build a kmp- on obs, do you see any kind of problem? (mostly license)
Building a KMP on OBS is very common. But make sure that the driver has a compliant FLOSS license.
At the end, I would like to get a easy as (zypper/kiwi) build to create a dedicated susestudio/kiwi build for this model so we could have something easy to install for grand-aunty ;-)
The first step would be to create a repository containing KMP and let people testing it. If there is a popular demand, it's even possible to merge the package to the official Leap repo. HTH, Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Sunday 22 November 2015 18.15:24 Takashi Iwai wrote:
On Sun, 22 Nov 2015 18:05:27 +0100, Bruno Friedmann wrote:
Hi, I'm looking for advise to ensure a good and long life to this kind of hardware.
http://www.intel.com/content/www/us/en/compute-stick/intel-compute-stick.htm...
I've took the stck1a32wfc (windows preloaded) due to better hardware.
The only thing that doesn't work out of the box is the Realtek wifi/bluetooth chipset.
a rtl8723bs
Fortunately there's one person that have good sources. https://github.com/hadess/rtl8723bs
So after installing Leap from usb key, and prepare the environment I've tested first the build install of the drivers without any kernel-patches. Connect but fail to handle network load etc...
hadess has some patches for kernel < 4.3 So good so far, I've patched the kernel and rebuild the whole (On the stick just for a try and science 320 minutes)
Once this patched 4.1.12 + the driver everything work now.
I've a perfect kodi (new xmbc name) connected on the tv.
I'm looking for your input on several points :
- Will the driver code end up in kernel one day?
To which kernel? openSUSE or upstream? Basically openSUSE kernel takes only changes from upstream, so it should be merged to upstream at first. Many Realtek drivers go via staging tree, so a fast way would be to ask the driver author to submit the driver patches to staging tree.
I was thinking about upstream ..
- What would be best way to maintain a derivative kernel on which I can add the needed patches ?
I don't think you need to patch the kernel itself to build the driver. Usually a driver can be built as an external module. For openSUSE, it's a KMP.
The list of patches are for kernel <4.3 (perhaps 4.4) So if I want to stay close to leap, I will have to patch the Leap 4.1 series
- I'm okay to build a kmp- on obs, do you see any kind of problem? (mostly license)
Building a KMP on OBS is very common. But make sure that the driver has a compliant FLOSS license.
Yeah it seems so.
At the end, I would like to get a easy as (zypper/kiwi) build to create a dedicated susestudio/kiwi build for this model so we could have something easy to install for grand-aunty ;-)
The first step would be to create a repository containing KMP and let people testing it. If there is a popular demand, it's even possible to merge the package to the official Leap repo.
HTH, Takashi
Many thanks for your comment I think I will open a branched Leap kernel (to apply the patch) What would be the best source for my osc bco to be able to follow kernel leap update https://build.opensuse.org/project/show/Kernel:openSUSE-42.1 look like a good candidate. But I wouldn't see obs rebuild my special kernel everyday :-) Once everything will be build and tested, I will publish it -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Mon, 23 Nov 2015 16:32:27 +0100, Bruno Friedmann wrote:
At the end, I would like to get a easy as (zypper/kiwi) build to create a dedicated susestudio/kiwi build for this model so we could have something easy to install for grand-aunty ;-)
The first step would be to create a repository containing KMP and let people testing it. If there is a popular demand, it's even possible to merge the package to the official Leap repo.
HTH, Takashi
Many thanks for your comment I think I will open a branched Leap kernel (to apply the patch) What would be the best source for my osc bco to be able to follow kernel leap update https://build.opensuse.org/project/show/Kernel:openSUSE-42.1 look like a good candidate.
But I wouldn't see obs rebuild my special kernel everyday :-)
Usually I set up two repos in the project, one for the stable release, openSUSE:Leap:42.1:Update, and another for the latest KOTD, Kernel:openSUSE-42.1. Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Sunday 22 of November 2015 18:05:27 Bruno Friedmann wrote:
The only thing that doesn't work out of the box is the Realtek wifi/bluetooth chipset.
a rtl8723bs
Fortunately there's one person that have good sources. https://github.com/hadess/rtl8723bs ... - Will the driver code end up in kernel one day?
As the github repository seems to belong to the person who maintains most Realtek wi-fi drivers in mainline kernel, I guess it's him whom you should ask about his plans about getting the driver into mainline. Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Monday 23 November 2015 07.08:12 Michal Kubecek wrote:
On Sunday 22 of November 2015 18:05:27 Bruno Friedmann wrote:
The only thing that doesn't work out of the box is the Realtek wifi/bluetooth chipset.
a rtl8723bs
Fortunately there's one person that have good sources. https://github.com/hadess/rtl8723bs ... - Will the driver code end up in kernel one day?
As the github repository seems to belong to the person who maintains most Realtek wi-fi drivers in mainline kernel, I guess it's him whom you should ask about his plans about getting the driver into mainline.
Michal Kubeček
Yeah found that information 15 minutes after sending the mail. It seems it will not be soon (several pointers to ml) So I will take the long path of osc bco kernel + patch another kmp for wifi + bt. Thanks -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 11/23/2015 12:08 AM, Michal Kubecek wrote:
On Sunday 22 of November 2015 18:05:27 Bruno Friedmann wrote:
The only thing that doesn't work out of the box is the Realtek wifi/bluetooth chipset.
a rtl8723bs
Fortunately there's one person that have good sources. https://github.com/hadess/rtl8723bs ... - Will the driver code end up in kernel one day?
As the github repository seems to belong to the person who maintains most Realtek wi-fi drivers in mainline kernel, I guess it's him whom you should ask about his plans about getting the driver into mainline.
The SDIO driver for the RTL8723BS is the same pile of stinking excrement as are all the Realtek drivers for USB devices, thus submission to the kernel requires many months of reworking. That applies even to staging. In addition, submission to staging also implies a commitment to eventually convert the driver for submission to the regular wireless tree. Actually, I do not expect to live long enough to be able to complete that task! There is hope. Jes Sorensen of Red Hat is writing a new driver for Realtek USB devices called rtl8xxxu. It lacks a number of features but is very stable. At the moment, it handles RTL8723AU, RTL8188(CR)U, and RTL819(1,2)CU. Jes is working on extending it to RTL8188EU and RTL8723BU. That last device is of great interest here. Once it works, it will be quite easy to add the SDIO plumbing in place of the USB stuff to make an rtl8723bs driver. Until that happens, you will need to use the GitHub repo that is referenced above. While awaiting the above developments, we are continuing to debug the GitHub driver to improve its stability. Larry -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Monday 23 November 2015 11.08:47 Larry Finger wrote:
On 11/23/2015 12:08 AM, Michal Kubecek wrote:
On Sunday 22 of November 2015 18:05:27 Bruno Friedmann wrote:
The only thing that doesn't work out of the box is the Realtek wifi/bluetooth chipset.
a rtl8723bs
Fortunately there's one person that have good sources. https://github.com/hadess/rtl8723bs ... - Will the driver code end up in kernel one day?
As the github repository seems to belong to the person who maintains most Realtek wi-fi drivers in mainline kernel, I guess it's him whom you should ask about his plans about getting the driver into mainline.
The SDIO driver for the RTL8723BS is the same pile of stinking excrement as are all the Realtek drivers for USB devices, thus submission to the kernel requires many months of reworking. That applies even to staging. In addition, submission to staging also implies a commitment to eventually convert the driver for submission to the regular wireless tree. Actually, I do not expect to live long enough to be able to complete that task!
There is hope. Jes Sorensen of Red Hat is writing a new driver for Realtek USB devices called rtl8xxxu. It lacks a number of features but is very stable. At the moment, it handles RTL8723AU, RTL8188(CR)U, and RTL819(1,2)CU. Jes is working on extending it to RTL8188EU and RTL8723BU. That last device is of great interest here. Once it works, it will be quite easy to add the SDIO plumbing in place of the USB stuff to make an rtl8723bs driver. Until that happens, you will need to use the GitHub repo that is referenced above.
While awaiting the above developments, we are continuing to debug the GitHub driver to improve its stability.
Larry
Many Many thanks Larry for your input, it make my path really clear :-) I've seen news that intel what to move away from Realtek in a near future for those compute stick and use one of their chip in 2016 :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (4)
-
Bruno Friedmann -
Larry Finger -
Michal Kubecek -
Takashi Iwai