Re: [opensuse-arm] SR for openSUSE:13.1:Ports kernel
On 27.04.14 17:23, Matwey V. Kornilov wrote:
I don't know. If it is the best solution, then we can. Basically, what I need is to fetch the 11 patches from Kernel:openSUSE-13.1 However, I am not aware of how does kernel updates usually get into Ports tree.
Please don't top post :). I don't think we have a really good solution for this. The "usual" way we envisioned things to work is that openSUSE:<release> just contains everything necessary for the release. Any board we have to enable after that process should just get a Contrib subproject where we can add newer versions of kernels etc specific to that board. In parallel all the changes go into Factory where we can then enable that board for the next <release> version of openSUSE. However, getting hardware support working for a release is so incredibly hard that I'm fairly sure we'd end up with an empty set of hardware platforms if we really went with that plan. So we started loosing up the requirements. I'm not sure up to which point it does make sense to loosen them though. Would it help you if we create a Contrib for the BeagleBone and add you as admin for that? There you could linkpac the JeOS package inside and copypac the latest kernel and then have your own playing ground for that particular platform without necessarily relying on us. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2014-04-27 21:53 GMT+04:00 Alexander Graf <agraf@suse.de>:
Please don't top post :).
Sorry, it is my moronic Android.
Any board we have to enable after that process should just get a Contrib subproject where we can add newer versions of kernels etc specific to that board. In parallel all the changes go into Factory where we can then enable that board for the next <release> version of openSUSE.
Ah, ok. I was confused by the fact that there already was JeOS-beaglebone package which obviously did not work due to some bugs in the kernel. However, we don't need something specific for beaglebone, Factory works great out of the box having the newer kernel.
Would it help you if we create a Contrib for the BeagleBone and add you as admin for that? There you could linkpac the JeOS package inside and copypac the latest kernel and then have your own playing ground for that particular platform without necessarily relying on us.
Would be great, given that you remove JeOS/XFCE-beaglebone from 13.1:Ports, because too many people tries to use it. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, 28 Apr 2014 12:50:26 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-04-27 21:53 GMT+04:00 Alexander Graf <agraf@suse.de>:
Please don't top post :).
Sorry, it is my moronic Android.
Any board we have to enable after that process should just get a Contrib subproject where we can add newer versions of kernels etc specific to that board. In parallel all the changes go into Factory where we can then enable that board for the next <release> version of openSUSE.
Ah, ok. I was confused by the fact that there already was JeOS-beaglebone package which obviously did not work due to some bugs in the kernel. However, we don't need something specific for beaglebone, Factory works great out of the box having the newer kernel.
Would it help you if we create a Contrib for the BeagleBone and add you as admin for that? There you could linkpac the JeOS package inside and copypac the latest kernel and then have your own playing ground for that particular platform without necessarily relying on us.
Would be great, given that you remove JeOS/XFCE-beaglebone from 13.1:Ports, because too many people tries to use it.
If the JEOS has networking, then you probably don't need the XFCE version since the user could load it. While I have the USB to serial cable, I noticed a rather blaring design bug in the Beaglebone Black. If you use the serial cable, you will not be able to connect a "cape". [Cape is the PCB that you attached via the two connectors on the BBB.] So I think JEOS should have networking. So which distribution of 13.1 Arm is supposed to work on the Beagle Bone Black? Gary -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 28.04.14 10:50, Matwey V. Kornilov wrote:
2014-04-27 21:53 GMT+04:00 Alexander Graf <agraf@suse.de>:
Please don't top post :). Sorry, it is my moronic Android.
Any board we have to enable after that process should just get a Contrib subproject where we can add newer versions of kernels etc specific to that board. In parallel all the changes go into Factory where we can then enable that board for the next <release> version of openSUSE. Ah, ok. I was confused by the fact that there already was JeOS-beaglebone package which obviously did not work due to some bugs in the kernel. However, we don't need something specific for beaglebone, Factory works great out of the box having the newer kernel.
Would it help you if we create a Contrib for the BeagleBone and add you as admin for that? There you could linkpac the JeOS package inside and copypac the latest kernel and then have your own playing ground for that particular platform without necessarily relying on us. Would be great, given that you remove JeOS/XFCE-beaglebone from 13.1:Ports, because too many people tries to use it.
Ok, done. When you need to do modifications to the .kiwi files, please modify them and sr the changes back into 13.1:Ports/JeOS. That way we keep at least the image description consistent between all flavors. The contrib repository is also part of the image build now, so whatever packages you put in there are available during the image build as well as in the installed system. It's great to hear that Factory images work. That means for the next openSUSE release we can just move the beaglebone from contrib status to fully integrated :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Alexander Graf -
lists -
Matwey V. Kornilov