Hi Tim.
The program is also now better structured, IMHO.
-- Tim
Seeing this programs gets frequent updates (good!) I have not
yet applied it.
When you consider it stabilized could you please drop me a
new mail including full changelog and updated patch.
And please cc: [EMAIL PROTECTED] +
On Thu, Jun 12, 2008 at 11:50 AM, David Woodhouse wrote:
On Thu, 2008-06-12 at 08:23 -0700, Tim Bird wrote:
Rob Landley wrote:
However, having one or more full-time engineers devoted to debugging
cross-compile issues is quite a high price to pay too. Moore's law really
doesn't help that
David Woodhouse wrote:
... fixing
them in the upstream packages (or in the autoconf system itself).
Once someone fixes the cross-compilation issues for a package, they usually
stay fixed, if the fixes are mainlined.
I don't think that's true, unfortunately. Autoconf makes it _easy_ to do
Guys:
If you opt to cross-compile, having to deal with those
sorts of things is the price you pay.
If the build system derives from autoconf, then a hacked-up config.cache (or
equivalent command-line args) often solves problems for me. Just give the cache
the answers that it would otherwise
On Thu, Jun 12, 2008 at 5:53 PM, Tim Bird wrote:
Mike Frysinger wrote:
Er, is that GPL or LGPL code that you're modifying? If so, you *have* to
push those code changes out (make them available to others), whether you
think people will be interested or not!
umm, not really. only if (1) he
On Thu, 2008-06-12 at 17:28 -0400, Glenn Henshaw wrote:
On Thu, Jun 12, 2008 at 3:35 PM, Marcus Tangermann wrote:
we currently try to boot a 2.6.21 kernel
time to upgrade
Wrong answer!!!
Many embedded devices can't upgrade kernels easily because of
customer requirements and
On Thu, Jun 12, 2008 at 05:46:42PM -0400, Mike Frysinger wrote:
On Thu, Jun 12, 2008 at 5:42 PM, James Chapman wrote:
David VomLehn wrote:
Amen, brother. I'm fortunate in that I work for an organization that is
quite good about enforcing code reviews, specifically, the QA organization
is
hi,
In my application I want to override the timer interrupt, and I'm
doing in this manner:
disable_irq(0); /* disable timer irq first */
free_irq(0, NULL); /* free the old irq */
setup_irq(0, new_irq0);
setup_irq() return with 0, however I got the
On Thu, Jun 12, 2008 at 10:52:44PM +0500, Shaz wrote:
I have been following Re: [PATCH 0/1] Embedded Maintainer(s) and
felt like asking that is there one good way to get a cross compiler
work. I tried buildroot, scratchbox and even openMoko with
openEmbedded but all of them had lots of issues
