On Mon, 2012-04-09 at 16:44 -0500, Mark Hatle wrote:
Depends on the distribution and reasons for these feeds. What is typical is
that a base distribution will be generated for a common compatible
(reasonable)
architecture.. i.e. armv5 -- with specific optimized package (glibc, openssl,
On 4/10/12 4:23 AM, Phil Blundell wrote:
On Mon, 2012-04-09 at 16:44 -0500, Mark Hatle wrote:
Depends on the distribution and reasons for these feeds. What is typical is
that a base distribution will be generated for a common compatible (reasonable)
architecture.. i.e. armv5 -- with specific
On Tue, 2012-04-10 at 12:39 -0500, Mark Hatle wrote:
The installation system uses a best
to least best match when doing assembly actions. So if the part is an
ARMv7a,
it will first look for ARMv7a w/ thumb, vfp and neon, not finding that,
ARMv7a
w/ thumb and vfp, then ARMv7a w/ thumb,
On 4/9/12 4:03 PM, Phil Blundell wrote:
On Mon, 2012-04-09 at 15:25 -0500, Mark Hatle wrote:
And just to be extra clear, I consider it a defect if we can produce a package
with the same name for two different tune settings.. (the exception being the
hell that is ARM and thumb namings.)
While
On Mon, 2012-04-09 at 16:21 -0500, Mark Hatle wrote:
I do, and thus the hell that is ARM. I could not currently generate a single
package feed that work would on a variety of devices (like a traditional
workstaton/server Linux OS would.)
Well, actually, you could in fact do exactly that.
On 4/9/12 4:30 PM, Phil Blundell wrote:
On Mon, 2012-04-09 at 16:21 -0500, Mark Hatle wrote:
I do, and thus the hell that is ARM. I could not currently generate a single
package feed that work would on a variety of devices (like a traditional
workstaton/server Linux OS would.)
Well,
