From: "Mark Gollahon" <golly@stellarwerx.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New IXP4XX-based Machine
Date: Thu, 01 Feb 2007 21:40:20 -0500 (EST) [thread overview]
Message-ID: <1170384018.15409@gatekeeper.stellarwerx.com> (raw)
In-Reply-To: <45C27C89.2040300@whitby.id.au>
[-- Attachment #1: Type: text/plain, Size: 2561 bytes --]
Rod Whitby wrote ..
> Mark Gollahon wrote:
> > Rod Whitby wrote ..
> >> That was a bug in the newly rewritten ixp4xx conf which I
> >> believe is now fixed.
> >
> > Great! When was the diff applied? I'd like to get it.
>
> Probably on Sunday:
> Commit by rwhitby on org.oe.dev :: r0e933978... / (26 files in 10 dirs):
> ixp4xx-related files: Replaced IXP4XX_MACHINE_ENDIAN with
> SITEINFO_ENDIANESS throughout OE, removing all instances of
> ixp4xx-specific ENDIAN checks in the OE metadata.
>
> > Right now its not much more than a bunch of MACHINE_EXTRA_RDEPENDS and
> > MACHINE_EXTRA_RRECOMMENDS settings thanks to your changes. However,
> there
> > is an embedded four-port eth switch chip in the box. Since the
> > manufacturer had to patch a number of areas in the Intel drivers to get
> it
> > to work originally, I am expecting to have to do the same with the GPL
> > ixp4xx eth drivers. That would mean kernel patches, which would probably
> > mean its own kernel .bb, etc.
>
> Actually, it would be good for you to talk to the GPL ethernet driver
> author, and get those patches upstream.
I will once I've determined that patches are necessary. I'm really hoping they aren't - but I'm not "holding my breath"....
> > From what I've seen of OE, it seems easier
> > to support a new machine .conf along with its own kernel .bb than trying
> > to shim a new kernel config in an old machine .conf (oh, BTW, to build
> for
> > *this machine*, you have to use *that machine's* .conf file, but make
> > PREFERRED_PROVIDER_virtual/kernel be *this*). Newbies are already
> > overwhelmed by OE's sheer configurability, throwing yet another exception
> > in on this just doesn't seem right to me.
>
> Agreed. What's the machine? Got any internal photos ;-)
It is an Arlotto SG205. They also have an SG305, but I don't have access to that machine or know its contents. However if the mainboard is any indication, its got at least a mini-pci slot more than the SG205. I'm sending pics along with this message. Hope you don't mind the megabyte pics. Figured it would give you a better look that way.
> >> I'm willing to work with you to get this right.
> >
> > I know - thank you. I just wish I had discovered what was the issue
> with
> > building the root filesys image before now....
>
> Let's work together, and make sure that ixp4xx{be,le}.conf are files
> that can be used for (included in) a number of such machine configurations.
Sounds good to me!
Regards,
-Mark Gollahon
prev parent reply other threads:[~2007-02-02 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 22:15 New IXP4XX-based Machine Mark Gollahon
2007-02-01 20:58 ` Rod Whitby
2007-02-01 22:48 ` Mark Gollahon
2007-02-01 23:49 ` Rod Whitby
2007-02-02 2:40 ` Mark Gollahon [this message]
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=1170384018.15409@gatekeeper.stellarwerx.com \
--to=golly@stellarwerx.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox