All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Marcin Juszkiewicz <openembedded@hrw.one.pl>
Cc: openembedded-devel@lists.openembedded.org,
	angstrom-distro-devel@linuxtogo.org
Subject: Re: Status of ARM machines in OE
Date: Wed, 10 Jan 2007 16:06:38 +0200	[thread overview]
Message-ID: <1132961128.20070110160638@gmail.com> (raw)
In-Reply-To: <200701092322.34825.openembedded@hrw.one.pl>

Hello Marcin,

Wednesday, January 10, 2007, 12:22:34 AM, you wrote:

> Dnia wtorek, 9 stycznia 2007 23:09, Rolf Leggewie napisał:
>> > I did "angstrom-2007.1-oabi" build for collie, h3600, h3800, simpad,
>> > compulab-pxa270. Results:
>>
>> Do I see signs of collie being supported in angstrom?

> If collie will meet common rules then yes. 

> Common rules:

> - 2.6 kernel
> - atleast 2 machine mentors in Angstrom

  Now, 2? Isn't that too steep? It's understood when 2 or more people
required to support some big software system, but what about machines?
Such requirement is simply not realistic for most of them. Of HH.org
machines, only hx4700 would qualify fully. Even for h2200 that would
be questionable, but thanks god, Koen has it, so assuming Matt Reimer
mentors it, it is safe.

  With such rules, there won't be Linux for PDA any time soon, only
Linux for Zauruses, Linux for iPaq hx4700, and other toy Linuxes.

  What's really required here is a point of view change. It would be
ludicrous to think that Debian would require two maintainers for each
motherboard model of each vendor. Debian simply doesn't deal with such
things as motherboards. It supports specific CPU architectures, that's
enough. And at the same time Linux distros for PDAs are obsessed over
PDA motherboards. There's even animism tendencies considering that
"machine" is something more than a tag given to some motherboard
implementation of the architecture, but also a bootloader spirit lives
there, and by conjuring it away one can beshrew rage of gods, etc.,
etc.

  So, stepping away from that towards architecture implementations as
such, I may offer myself as a mentor for all handhelds.org-maintained
machines. In 2.6 kernels, we have all the needed commonality and
generality (and work towards more) to treat all our machines
consistently. So, what's really required is someone to physically test
boot on a machine, and that's enough. Not boot means upstream (hh.org)
kernel problem, otherwise, it works (bugs are either common or due to
specific kernel bug also).



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  parent reply	other threads:[~2007-01-10 14:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 15:18 Status of ARM machines in OE Marcin Juszkiewicz
2007-01-08 15:28 ` Marcin Juszkiewicz
2007-01-08 16:03 ` Justin Patrin
2007-01-08 16:08   ` Koen Kooi
2007-01-08 18:12     ` Erik Hovland
2007-01-09  7:50   ` Marcin Juszkiewicz
2007-01-08 16:19 ` Cliff Brake
2007-01-08 16:22   ` Koen Kooi
2007-01-08 17:52     ` Richard Purdie
2007-01-08 18:10       ` Koen Kooi
2007-01-08 18:23         ` Paul Sokolovsky
2007-01-08 18:34           ` Koen Kooi
2007-01-08 19:34   ` Marcin Juszkiewicz
2007-01-09 13:30     ` Marcin Juszkiewicz
2007-01-09 13:34       ` Koen Kooi
2007-01-09 22:09       ` Rolf Leggewie
2007-01-09 22:22         ` Marcin Juszkiewicz
2007-01-10 13:00           ` Rolf Leggewie
2007-01-10 13:32             ` Marcin Juszkiewicz
2007-01-10 18:51               ` Rolf Leggewie
2007-01-10 14:06           ` Paul Sokolovsky [this message]
2007-01-10 14:38             ` Koen Kooi
2007-01-10 14:54               ` [Angstrom-devel] " Paul Sokolovsky
2007-01-08 17:18 ` pHilipp Zabel
2007-01-09 18:07 ` Paul Sokolovsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1132961128.20070110160638@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded@hrw.one.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.