[opensuse-arm] armv5 and armv6 questions
Hi, Will armv5 be dropped or have we only shutdown armv5 scheduler temporary? Which armv6 repo should we use? There are : openSUSE:Factory:ARM:armv6hl/armv6l and openSUSE:Factory:ARM:standard/armv6l. Regards, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 27. Juni 2013, 09:43:56 schrieb Guillaume Gardet:
Hi,
Will armv5 be dropped or have we only shutdown armv5 scheduler temporary?
right now it is temporary, until we get our second OBS binary backend. But if no one cares about armv5, we could also drop it.
Which armv6 repo should we use? There are : openSUSE:Factory:ARM:armv6hl/armv6l and openSUSE:Factory:ARM:standard/armv6l.
The "standard" one is the one which is planned to be the official one. Currently it only contains armv7 binaries so that a boot strap can be started. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Guillaume,
Which armv6 repo should we use? There are : openSUSE:Factory:ARM:armv6hl/armv6l and
At the moment I use armv6hl/armv6l to (try to) bootstrap an armv6 distro. it is not there yet.
openSUSE:Factory:ARM:standard/armv6l.
That one is some temporary hack from adrian, ignore it for now. it will go away or be replaced by armv6hl once the bootstrap actually succeeded. I think it would be a good idea to get the 12.3 sources built for armv6l (the scheduler) so that you can continue on hacking kiwi+imaging. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 27. Juni 2013, 11:41:06 schrieb Dirk Müller:
Hi Guillaume,
Which armv6 repo should we use? There are : openSUSE:Factory:ARM:armv6hl/armv6l and
At the moment I use armv6hl/armv6l to (try to) bootstrap an armv6 distro. it is not there yet.
openSUSE:Factory:ARM:standard/armv6l.
That one is some temporary hack from adrian, ignore it for now. it will go away or be replaced by armv6hl once the bootstrap actually succeeded.
??? no, it will the official one. It contains the rpms you asked for. And I do not see a reason to start an additional armv6hl scheduler. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 27/06/2013 11:41, Dirk Müller a écrit :
Hi Guillaume,
Which armv6 repo should we use? There are : openSUSE:Factory:ARM:armv6hl/armv6l and At the moment I use armv6hl/armv6l to (try to) bootstrap an armv6 distro. it is not there yet.
ok
openSUSE:Factory:ARM:standard/armv6l. That one is some temporary hack from adrian, ignore it for now. it will go away or be replaced by armv6hl once the bootstrap actually succeeded.
ok. What would be the better name: armv6l or armv6hl? Kernel uses armv6l but I guess for us armv6l would be for soft-float and armv6hl for hardfloat?
I think it would be a good idea to get the 12.3 sources built for armv6l (the scheduler) so that you can continue on hacking kiwi+imaging.
Yes. Could you do it for me, please? Guillaume
Greetings, Dirk
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hey Guillaume,
ok. What would be the better name: armv6l or armv6hl? Kernel uses armv6l but I guess for us armv6l would be for soft-float and armv6hl for hardfloat?
Well, I agree that it is confusing but I made it consistent with armv7hl/armv7l, so it doesn't add an extra layer to the confusions of how to build ARM in the Open Build Service. The RPM distros agreed to use hl for hardfloat distros as a rpm architecture, so I think we should use that one as well (See the same done for e.g. Fedora here: http://japan.proximity.on.ca/koji/). For reasons that I don't understand/remember, the OBS uses however uname -m, so thats where the armv6l is coming from.
I think it would be a good idea to get the 12.3 sources built for armv6l (the scheduler) so that you can continue on hacking kiwi+imaging. Yes. Could you do it for me, please?
I'll need Adrian's powers for that. I'll try to look into it later. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 27. Juni 2013, 12:15:30 schrieb Dirk Müller:
Hey Guillaume,
ok. What would be the better name: armv6l or armv6hl? Kernel uses armv6l but I guess for us armv6l would be for soft-float and armv6hl for hardfloat? Well, I agree that it is confusing but I made it consistent with armv7hl/armv7l, so it doesn't add an extra layer to the confusions of how to build ARM in the Open Build Service. The RPM distros agreed to use hl for hardfloat distros as a rpm architecture, so I think we should use that one as well (See the same done for e.g. Fedora here: http://japan.proximity.on.ca/koji/).
For reasons that I don't understand/remember, the OBS uses however uname -m, so thats where the armv6l is coming from.
it is not uname -m, it is manual setup decision. But it is the same as the kernel does it (it does not know armv7hl either). We can rename all schedulers to hl, but we should do it consistent. And it is kind of a problem, because we already release a v7l distro.
I think it would be a good idea to get the 12.3 sources built for armv6l (the scheduler) so that you can continue on hacking kiwi+imaging.
Yes. Could you do it for me, please?
I'll need Adrian's powers for that. I'll try to look into it later.
for what? Just setting up a project link using openSUSE:Factory:ARM/standard (containing armv6l) would not work? I thought that is what you wanted the armv7 binaries inside for ? -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Adrian,
For reasons that I don't understand/remember, the OBS uses however uname -m, so thats where the armv6l is coming from. it is not uname -m, it is manual setup decision. But it is the same as the kernel does it (it does not know armv7hl either).
Thats uname -m then.
for what? Just setting up a project link using openSUSE:Factory:ARM/standard (containing armv6l) would not work? I thought that is what you wanted the armv7 binaries inside for ?
We're not talking about factory but about 12.3. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 27/06/2013 14:02, Dirk Müller a écrit :
Hi Adrian,
For reasons that I don't understand/remember, the OBS uses however uname -m, so thats where the armv6l is coming from. it is not uname -m, it is manual setup decision. But it is the same as the kernel does it (it does not know armv7hl either). Thats uname -m then.
for what? Just setting up a project link using openSUSE:Factory:ARM/standard (containing armv6l) would not work? I thought that is what you wanted the armv7 binaries inside for ? We're not talking about factory but about 12.3.
Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)? Guillaume
Greetings, Dirk
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:02, Dirk Müller a écrit :
Hi Adrian,
For reasons that I don't understand/remember, the OBS uses however uname -m, so thats where the armv6l is coming from.
it is not uname -m, it is manual setup decision. But it is the same as the kernel does it (it does not know armv7hl either).
Thats uname -m then.
for what? Just setting up a project link using openSUSE:Factory:ARM/standard (containing armv6l) would not work? I thought that is what you wanted the armv7 binaries inside for ?
We're not talking about factory but about 12.3.
Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)?
that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 27/06/2013 14:46, Adrian Schröter a écrit :
Le 27/06/2013 14:02, Dirk Müller a écrit :
Hi Adrian,
For reasons that I don't understand/remember, the OBS uses however uname -m, so thats where the armv6l is coming from. it is not uname -m, it is manual setup decision. But it is the same as the kernel does it (it does not know armv7hl either). Thats uname -m then.
for what? Just setting up a project link using openSUSE:Factory:ARM/standard (containing armv6l) would not work? I thought that is what you wanted the armv7 binaries inside for ? We're not talking about factory but about 12.3. Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)?
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet: that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well.
Ok, thanks. Any links, please? armv5 -> armv6 will be more usefull since I can get a working image on Raspberry Pi whereas armv7 stuff won't run. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 27. Juni 2013, 14:50:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:46, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:02, Dirk Müller a écrit :
Hi Adrian,
For reasons that I don't understand/remember, the OBS uses however uname -m, so thats where the armv6l is coming from.
it is not uname -m, it is manual setup decision. But it is the same as the kernel does it (it does not know armv7hl either).
Thats uname -m then.
for what? Just setting up a project link using openSUSE:Factory:ARM/standard (containing armv6l) would not work? I thought that is what you wanted the armv7 binaries inside for ?
We're not talking about factory but about 12.3.
Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)?
that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well.
Ok, thanks. Any links, please? armv5 -> armv6 will be more usefull since I can get a working image on Raspberry Pi whereas armv7 stuff won't run.
all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 27/06/2013 16:34, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:50:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:46, Adrian Schröter a écrit :
Le 27/06/2013 14:02, Dirk Müller a écrit :
Hi Adrian,
> For reasons that I don't understand/remember, the OBS uses however > uname -m, so thats where the armv6l is coming from. it is not uname -m, it is manual setup decision. But it is the same as the kernel does it (it does not know armv7hl either). Thats uname -m then.
for what? Just setting up a project link using openSUSE:Factory:ARM/standard (containing armv6l) would not work? I thought that is what you wanted the armv7 binaries inside for ? We're not talking about factory but about 12.3. Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)?
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet: that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well. Ok, thanks. Any links, please? armv5 -> armv6 will be more usefull since I can get a working image on Raspberry Pi whereas armv7 stuff won't run. all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now.
Would it be possible to create devel:ARM:12.3:Contrib:RaspberryPi/images armv6l? So that I can link to it? (because I have some problems to set up correctly my home images repo ATM). Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 27. Juni 2013, 17:05:40 schrieb Guillaume Gardet:
Le 27/06/2013 16:34, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:50:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:46, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:02, Dirk Müller a écrit :
Hi Adrian,
>> For reasons that I don't understand/remember, the OBS uses however >> uname -m, so thats where the armv6l is coming from. > > it is not uname -m, it is manual setup decision. But it is the same > as > the kernel does it (it does not know armv7hl either).
Thats uname -m then.
> for what? Just setting up a project link using > openSUSE:Factory:ARM/standard (containing armv6l) would not work? I > thought that is what you wanted the armv7 binaries inside for ?
We're not talking about factory but about 12.3.
Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)?
that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well.
Ok, thanks. Any links, please? armv5 -> armv6 will be more usefull since I can get a working image on Raspberry Pi whereas armv7 stuff won't run.
all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now.
Would it be possible to create devel:ARM:12.3:Contrib:RaspberryPi/images armv6l? So that I can link to it? (because I have some problems to set up correctly my home images repo ATM).
done. Maybe it would make more sense to add you to the project owner list, but I will leave that to the current owners. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 27/06/2013 17:08, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 17:05:40 schrieb Guillaume Gardet:
Le 27/06/2013 16:34, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:50:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:46, Adrian Schröter a écrit :
Le 27/06/2013 14:02, Dirk Müller a écrit : > Hi Adrian, > >>> For reasons that I don't understand/remember, the OBS uses however >>> uname -m, so thats where the armv6l is coming from. >> it is not uname -m, it is manual setup decision. But it is the same >> as >> the kernel does it (it does not know armv7hl either). > Thats uname -m then. > >> for what? Just setting up a project link using >> openSUSE:Factory:ARM/standard (containing armv6l) would not work? I >> thought that is what you wanted the armv7 binaries inside for ? > We're not talking about factory but about 12.3. Maybe it needs too much work and we could just use a snapshot of Factory (once it will be ready)?
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet: that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well. Ok, thanks. Any links, please? armv5 -> armv6 will be more usefull since I can get a working image on Raspberry Pi whereas armv7 stuff won't run. all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now. Would it be possible to create devel:ARM:12.3:Contrib:RaspberryPi/images armv6l? So that I can link to it? (because I have some problems to set up correctly my home images repo ATM). done.
Thanks. It seems OBS is quite slow ATM. armv6l does not show up yet: https://build.opensuse.org/project/show?project=devel%3AARM%3A12.3%3AContrib... whereas repo config show that armv6l is enabled for images. Or maybe there is a problem? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 27. Juni 2013, 17:29:51 schrieb Guillaume Gardet:
Le 27/06/2013 17:08, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 17:05:40 schrieb Guillaume Gardet:
Le 27/06/2013 16:34, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:50:41 schrieb Guillaume Gardet:
Le 27/06/2013 14:46, Adrian Schröter a écrit :
Am Donnerstag, 27. Juni 2013, 14:45:41 schrieb Guillaume Gardet: > Le 27/06/2013 14:02, Dirk Müller a écrit : >> Hi Adrian, >> >>>> For reasons that I don't understand/remember, the OBS uses however >>>> uname -m, so thats where the armv6l is coming from. >>> >>> it is not uname -m, it is manual setup decision. But it is the same >>> as >>> the kernel does it (it does not know armv7hl either). >> >> Thats uname -m then. >> >>> for what? Just setting up a project link using >>> openSUSE:Factory:ARM/standard (containing armv6l) would not work? I >>> thought that is what you wanted the armv7 binaries inside for ? >> >> We're not talking about factory but about 12.3. > > Maybe it needs too much work and we could just use a snapshot of > Factory > (once it will be ready)?
that one is there since yesterday, but a armv5 -> armv6 copy for 12.3 is running now as well.
Ok, thanks. Any links, please? armv5 -> armv6 will be more usefull since I can get a working image on Raspberry Pi whereas armv7 stuff won't run.
all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now.
Would it be possible to create devel:ARM:12.3:Contrib:RaspberryPi/images armv6l? So that I can link to it? (because I have some problems to set up correctly my home images repo ATM).
done.
Thanks. It seems OBS is quite slow ATM. armv6l does not show up yet: https://build.opensuse.org/project/show?project=devel%3AARM%3A12.3%3AContrib %3ARaspberryPi
whereas repo config show that armv6l is enabled for images.
Or maybe there is a problem?
it is still scanning the repo -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri 28 Jun 2013 02:34:33 NZST +1200, Adrian Schröter wrote:
all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now.
Good, thanks. What was the particular reason to start naming packages armv5 for an ARMv6 architecture? It seems to have created one hell of a confusion. Can those in the know please make sure the wiki pages are updated, so users have a chance to work out what they should use without having to go around the mailing list? Thanks muchly, Volker -- Volker Kuhlmann http://volker.dnsalias.net/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Freitag, 28. Juni 2013, 10:46:01 schrieb Volker Kuhlmann:
On Fri 28 Jun 2013 02:34:33 NZST +1200, Adrian Schröter wrote:
all armv5 rpms of devel:ARM:12.3:Contrib:RaspberryPi standard repo are copied to the armv6 one now.
Good, thanks. What was the particular reason to start naming packages armv5 for an ARMv6 architecture? It seems to have created one hell of a confusion.
they are just the base to bootstrap armv6. Every new build will be named armv6hl. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Volker,
Good, thanks. What was the particular reason to start naming packages armv5 for an ARMv6 architecture? It seems to have created one hell of a confusion.
Thats actually a misunderstanding. The packages that were called armv5 were actually for ARMv5. Its just that those happen to be compatible with ARMv6. We are just *creating* a ARMv6 distribution.
Can those in the know please make sure the wiki pages are updated, so users have a chance to work out what they should use without having to go around the mailing list?
Sure, which wiki page in particular do you have in mind? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Adrian Schröter -
Dirk Müller -
Guillaume Gardet -
Volker Kuhlmann