[opensuse-arm] Ideas to improve ARM in openSUSE
Hi, Just some ideas. It would be nice to: * Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?) * Improve kernel configs and maybe have a system to follow and update ARM configs (common/specific options) (a (wiki) table, a spreadsheet, or something else which is easily editable and easy to use). Maybe some tools already exist? * Have some pages on the wiki which tell users how to use openSUSE images for their ARM board. * Have some pages on the wiki which tell users (and developpers) what is the support level of a given board (USB OK, Ethernet KO, etc.). I started some wiki things on my user page: http://en.opensuse.org/User:Guillaume_G Feel free to edit it if needed. I will move it to real wiki pages once there are enough infos. Is there a preferred wiki structure or namespace? Or only use Category:ARM and links from Portal:ARM are enough? It would be interesting to know who use which board to have a good start for supported hardware. Maybe add support for raspberry Pi could be interesting even if it is an ARMv6. What must be done to add armv5 kernel configs and maybe kiwi image? If you have more ideas, please share! Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 01.05.2012 19:25, schrieb Guillaume Gardet:
Hi,
Just some ideas.
It would be nice to: * Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?) * Improve kernel configs and maybe have a system to follow and update ARM configs (common/specific options) (a (wiki) table, a spreadsheet, or something else which is easily editable and easy to use). Maybe some tools already exist? * Have some pages on the wiki which tell users how to use openSUSE images for their ARM board. * Have some pages on the wiki which tell users (and developpers) what is the support level of a given board (USB OK, Ethernet KO, etc.).
I started some wiki things on my user page: http://en.opensuse.org/User:Guillaume_G Feel free to edit it if needed. I will move it to real wiki pages once there are enough infos. Is there a preferred wiki structure or namespace? Or only use Category:ARM and links from Portal:ARM are enough?
It would be interesting to know who use which board to have a good start for supported hardware.
I have the pandaboard ES and can do some testing in my spare time. Until now I still use the Build10.1 image (w/o WIFI support). Is it possible to upgrade via "zypper up" meanwhile? My last try wasn't successful (http://lists.opensuse.org/opensuse-arm/2012-04/msg00026.html).
Maybe add support for raspberry Pi could be interesting even if it is an ARMv6. What must be done to add armv5 kernel configs and maybe kiwi image?
If you have more ideas, please share!
Cheers,
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 01/05/2012 22:10, endym a écrit :
Am 01.05.2012 19:25, schrieb Guillaume Gardet:
Hi,
Just some ideas.
It would be nice to: * Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?) * Improve kernel configs and maybe have a system to follow and update ARM configs (common/specific options) (a (wiki) table, a spreadsheet, or something else which is easily editable and easy to use). Maybe some tools already exist? * Have some pages on the wiki which tell users how to use openSUSE images for their ARM board. * Have some pages on the wiki which tell users (and developpers) what is the support level of a given board (USB OK, Ethernet KO, etc.).
I started some wiki things on my user page: http://en.opensuse.org/User:Guillaume_G Feel free to edit it if needed. I will move it to real wiki pages once there are enough infos. Is there a preferred wiki structure or namespace? Or only use Category:ARM and links from Portal:ARM are enough?
It would be interesting to know who use which board to have a good start for supported hardware.
I have the pandaboard ES and can do some testing in my spare time. Until now I still use the Build10.1 image (w/o WIFI support). Is it possible to upgrade via "zypper up" meanwhile? My last try wasn't successful (http://lists.opensuse.org/opensuse-arm/2012-04/msg00026.html).
There is a 10.2 image available for pandaboard but I am not sure if there are some improvements between 10.1 and 10.2 images. You can get the kernel version with 'uname -a'. Then, you can report tests with USB host, USB OTG, SD/MMC, Audio In, audio Out, Ethernet, UART, DVI, HDMI, Bluetooth and WiFi. New kernel with wifi support is not yet available. Do you know if you need calibration [0] for your wifi? 'zypper up' may break your board again since kernel update is not yet handle for the bootloader. I think it should be done for next images. Thanks. Guillaume [0]: http://linuxwireless.org/en/users/Drivers/wl12xx/calibrator -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 02.05.2012 09:48, schrieb Guillaume Gardet:
Le 01/05/2012 22:10, endym a écrit :
Am 01.05.2012 19:25, schrieb Guillaume Gardet:
Hi,
Just some ideas.
It would be nice to: * Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?) * Improve kernel configs and maybe have a system to follow and update ARM configs (common/specific options) (a (wiki) table, a spreadsheet, or something else which is easily editable and easy to use). Maybe some tools already exist? * Have some pages on the wiki which tell users how to use openSUSE images for their ARM board. * Have some pages on the wiki which tell users (and developpers) what is the support level of a given board (USB OK, Ethernet KO, etc.).
I started some wiki things on my user page: http://en.opensuse.org/User:Guillaume_G Feel free to edit it if needed. I will move it to real wiki pages once there are enough infos. Is there a preferred wiki structure or namespace? Or only use Category:ARM and links from Portal:ARM are enough?
It would be interesting to know who use which board to have a good start for supported hardware.
I have the pandaboard ES and can do some testing in my spare time. Until now I still use the Build10.1 image (w/o WIFI support). Is it possible to upgrade via "zypper up" meanwhile? My last try wasn't successful (http://lists.opensuse.org/opensuse-arm/2012-04/msg00026.html).
There is a 10.2 image available for pandaboard but I am not sure if there are some improvements between 10.1 and 10.2 images. You can get the kernel version with 'uname -a'. Then, you can report tests with USB host, USB OTG, SD/MMC, Audio In, audio Out, Ethernet, UART, DVI, HDMI, Bluetooth and WiFi.
I guess there will be a new image in the next couple of days, so I think it's more reasonable to do these tests then?! Are there any test cases/scripts defined or shall I perform some simple "good cases" tests?
New kernel with wifi support is not yet available. Do you know if you need calibration [0] for your wifi?
If I understand the description here (http://omappedia.org/wiki/Mac80211_based_open_source_architecture#Firmware_a...) right, all necessary files already exists in a git repository?! Anyway, it might be a good idea to configure the kernel to support a calibration: NL80211_TESTMODE=y (nl80211 testmode commands) CRC7=m FW_LOADER=m as recommened in [0]. As soon as an image with wifi enabled exists, I will try it first without calibration.
'zypper up' may break your board again since kernel update is not yet handle for the bootloader. I think it should be done for next images.
Thanks.
Guillaume
[0]: http://linuxwireless.org/en/users/Drivers/wl12xx/calibrator
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 02/05/2012 21:59, endym a écrit :
Am 02.05.2012 09:48, schrieb Guillaume Gardet:
Le 01/05/2012 22:10, endym a écrit :
Am 01.05.2012 19:25, schrieb Guillaume Gardet:
Hi,
Just some ideas.
It would be nice to: * Have some non-JeOS images : Desktop with Xfce, LXDE, E17, JWM or IceWM or something else which is light) (and server in text mode?) * Improve kernel configs and maybe have a system to follow and update ARM configs (common/specific options) (a (wiki) table, a spreadsheet, or something else which is easily editable and easy to use). Maybe some tools already exist? * Have some pages on the wiki which tell users how to use openSUSE images for their ARM board. * Have some pages on the wiki which tell users (and developpers) what is the support level of a given board (USB OK, Ethernet KO, etc.).
I started some wiki things on my user page: http://en.opensuse.org/User:Guillaume_G Feel free to edit it if needed. I will move it to real wiki pages once there are enough infos. Is there a preferred wiki structure or namespace? Or only use Category:ARM and links from Portal:ARM are enough?
It would be interesting to know who use which board to have a good start for supported hardware.
I have the pandaboard ES and can do some testing in my spare time. Until now I still use the Build10.1 image (w/o WIFI support). Is it possible to upgrade via "zypper up" meanwhile? My last try wasn't successful (http://lists.opensuse.org/opensuse-arm/2012-04/msg00026.html).
There is a 10.2 image available for pandaboard but I am not sure if there are some improvements between 10.1 and 10.2 images. You can get the kernel version with 'uname -a'. Then, you can report tests with USB host, USB OTG, SD/MMC, Audio In, audio Out, Ethernet, UART, DVI, HDMI, Bluetooth and WiFi.
I guess there will be a new image in the next couple of days, so I think it's more reasonable to do these tests then?! Are there any test cases/scripts defined or shall I perform some simple "good cases" tests?
Yes, you can wait for that. ATM, there are no test cases/scripts, just try if USB, DVI, HDMI, etc. are working fine. If you have time you can test your current image/kernel and then the next image to see if there are any improvements or regression.
New kernel with wifi support is not yet available. Do you know if you need calibration [0] for your wifi?
If I understand the description here (http://omappedia.org/wiki/Mac80211_based_open_source_architecture#Firmware_a...) right, all necessary files already exists in a git repository?! Anyway, it might be a good idea to configure the kernel to support a calibration: NL80211_TESTMODE=y (nl80211 testmode commands)
Unfortunatly NL80211_TESTMODE is not set. Is there something else you need for pandaboard?
CRC7=m FW_LOADER=m
They are already set.
as recommened in [0]. As soon as an image with wifi enabled exists, I will try it first without calibration.
Ok. Fine. Guillaume
'zypper up' may break your board again since kernel update is not yet handle for the bootloader. I think it should be done for next images.
Thanks.
Guillaume
[0]: http://linuxwireless.org/en/users/Drivers/wl12xx/calibrator
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 03/05/2012 10:38, Guillaume Gardet a écrit :
Le 02/05/2012 21:59, endym a écrit :
Am 02.05.2012 09:48, schrieb Guillaume Gardet:
Le 01/05/2012 22:10, endym a écrit :
Am 01.05.2012 19:25, schrieb Guillaume Gardet:
New kernel with wifi support is not yet available. Do you know if you need calibration [0] for your wifi?
If I understand the description here (http://omappedia.org/wiki/Mac80211_based_open_source_architecture#Firmware_a...) right, all necessary files already exists in a git repository?! Anyway, it might be a good idea to configure the kernel to support a calibration: NL80211_TESTMODE=y (nl80211 testmode commands)
Unfortunatly NL80211_TESTMODE is not set. Is there something else you need for pandaboard?
Kernel help about NL80211_TESTMODE says: "The nl80211 testmode command helps implementing things like factory calibration or validation tools for wireless chips. Select this option ONLY for kernels that are specifically built for such purposes. Debugging tools that are supposed to end up in the hands of users should better be implemented with debugfs. Say N." So, if it is done in factory, you should not need to do calibration. Am I right? I just see that WL12XX* are not enabled in the config files where as it should be. I will send a patch as soon as possible to enable it. Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Guillaume Gardet <guillaume.gardet@free.fr> schrieb:
Le 03/05/2012 10:38, Guillaume Gardet a écrit :
Le 02/05/2012 21:59, endym a écrit :
Am 02.05.2012 09:48, schrieb Guillaume Gardet:
Le 01/05/2012 22:10, endym a écrit :
Am 01.05.2012 19:25, schrieb Guillaume Gardet:
New kernel with wifi support is not yet available. Do you know if
you need calibration [0] for your wifi?
If I understand the description here
(http://omappedia.org/wiki/Mac80211_based_open_source_architecture#Firmware_a...) right, all necessary files already exists in a git repository?!
Anyway, it might be a good idea to configure the kernel to support a calibration: NL80211_TESTMODE=y (nl80211 testmode commands)
Unfortunatly NL80211_TESTMODE is not set. Is there something else you need for pandaboard?
Kernel help about NL80211_TESTMODE says: "The nl80211 testmode command helps implementing things like factory calibration or validation tools for wireless chips. Select this option ONLY for kernels that are specifically built for such purposes. Debugging tools that are supposed to end up in the hands of users should better be implemented with debugfs. Say N."
According to http://omappedia.org/wiki/Mac80211_based_open_source_architect ure#To_enable_WLAN_on_the_Panda_Bo ard_Linux_Kernel the "nl80211 testmode command" are needed for the iw tool.
So, if it is done in factory, you should not need to do calibration. Am I right?
My understanding is following: The wl12xx driver needs a NVS file suitable for the specific hardware design. If we can use the file from git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git then all is fine. Otherwise we have to generate the NVS file via the calibration process.
I just see that WL12XX* are not enabled in the config files where as it should be. I will send a patch as soon as possible to enable it.
Cheers,
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 03/05/2012 15:35, endym a écrit :
Guillaume Gardet<guillaume.gardet@free.fr> schrieb:
Le 03/05/2012 10:38, Guillaume Gardet a écrit :
Le 02/05/2012 21:59, endym a écrit :
Am 02.05.2012 09:48, schrieb Guillaume Gardet:
Le 01/05/2012 22:10, endym a écrit :
Am 01.05.2012 19:25, schrieb Guillaume Gardet: > New kernel with wifi support is not yet available. Do you know if
you need calibration [0] for your wifi?
If I understand the description here (http://omappedia.org/wiki/Mac80211_based_open_source_architecture#Firmware_a...) right, all necessary files already exists in a git repository?! Anyway, it might be a good idea to configure the kernel to support a calibration: NL80211_TESTMODE=y (nl80211 testmode commands) Unfortunatly NL80211_TESTMODE is not set. Is there something else you need for pandaboard?
Kernel help about NL80211_TESTMODE says: "The nl80211 testmode command helps implementing things like factory calibration or validation tools for wireless chips. Select this option ONLY for kernels that are specifically built for such purposes. Debugging tools that are supposed to end up in the hands of users should better be implemented with debugfs. Say N."
According to http://omappedia.org/wiki/Mac80211_based_open_source_architect ure#To_enable_WLAN_on_the_Panda_Bo ard_Linux_Kernel the "nl80211 testmode command" are needed for the iw tool.
Ok. I enabled it in kernel config.
So, if it is done in factory, you should not need to do calibration. Am I right? My understanding is following: The wl12xx driver needs a NVS file suitable for the specific hardware design. If we can use the file from git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git then all is fine. Otherwise we have to generate the NVS file via the calibration process.
Not sure if NVS file should be generated on a per chip basis (1 file for all WL12xx chips), per board design basis (1 file for all pandaboards) or per board basis (1 file for 1 pandaboard, not the same for all pandaboards). If the one from linux-firmware git is fine, we can use the kernel-firmware package. Anyway, if we have to generate it, we will be able to do so since it is enabled in kernel.
I just see that WL12XX* are not enabled in the config files where as it should be. I will send a patch as soon as possible to enable it.
As told just before, I enabled it in kernel config. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
endym -
Guillaume Gardet