All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@domain.hid>
To: Kent Borg <kentborg@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] heres a go at an	adeos-ipipe-2.6.15-i386-1.1-01.patch
Date: Sat, 07 Jan 2006 00:52:23 -0700	[thread overview]
Message-ID: <43BF7337.7020506@domain.hid> (raw)
In-Reply-To: <20060106163226.X16178@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]

Kent Borg wrote:

>Jim Cromie posted a patch attempt for 2.6.15 (yeah!), and the patch
>applied, but it doesn't compile for me:
>
>  [...]
>    LD      init/built-in.o
>    LD      .tmp_vmlinux1
>  arch/i386/kernel/built-in.o: In function `__ipipe_sync_stage':
>  : undefined reference to `ret_from_intr'
>  arch/i386/kernel/built-in.o: In function `__ipipe_sync_stage':
>  : undefined reference to `ret_from_intr'
>  make: *** [.tmp_vmlinux1] Error 1
>  ~/linux-2.6.15$ 
>
>For a .config I started with the stock Ubuntu 2.6.12-10-686 config
>file and then took the defaults for all the oldconfig questions.
>
>Suggestions?
>
>  
>
You get to keep both pieces ? ;-)


FWIW, the kernel was still running on my soekris 4801 til just now. (I 
rebooted)
Most of that time it was without its NFS root fs;
my laptop was unconnected.  It was doing *no* work of any kind tho.
Not that this helps...


Im trying a kernel build on my sony laptop pentium M.
differnt config than yours, but fuller than the soekris.
Its running now, Im typing on it.
wifi card works too !

Ive attached my working config - might get you going.
pls report back what made your config not work, once you find it.

::::::::::::::
ipipe/Linux
::::::::::::::
Priority=100, Id=0x00000000
irq0-15: accepted
irq32: grabbed, virtual
::::::::::::::
ipipe/version
::::::::::::::
1.1-01




FWIW, I diffed the 14 patch against mine, was puzzled at the large 
textual diffs.
Guessed that it was a file ordering diff in the tar, and then forgot to 
mention this
at send.  This seems kinda odd, since Im running linux.

Phillipe, are you running BSD  ?  </ducks>

Are you creating patches from an fs other than ext3 ?
That could explain the ordering.  If not, Im stumped.
Maybe its an svn thing, they have a berkley-db-as-fs dont they ?

hth,
jimc



Also, FWIW, Ive been reading LKML, and it appears that
Ingo Molnar's  Mutex patches have turned the corner with Linux.
Theyre not in, and Ive got no crystal ball, but I suspect they
will get into 17 or 16

a good writeup for the regular folks (like me) on this list is here:
http://lwn.net/Articles/164380/


[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 12891 bytes --]

  reply	other threads:[~2006-01-07  7:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 21:32 [Xenomai-core] heres a go at an adeos-ipipe-2.6.15-i386-1.1-01.patch Kent Borg
2006-01-07  7:52 ` Jim Cromie [this message]
2006-01-07  8:35   ` Hannes Mayer
2006-01-07 11:36   ` Philippe Gerum
2006-01-07 16:42   ` Kent Borg
2006-01-07 19:41     ` Philippe Gerum
2006-01-07 21:44       ` Jim Cromie
2006-01-07 22:16         ` Philippe Gerum
2006-01-08 10:48           ` Philippe Gerum
2006-01-08 16:08       ` Kent Borg
  -- strict thread matches above, loose matches on Subject: below --
2006-01-05  2:43 Jim Cromie
2006-01-05 13:53 ` Philippe Gerum

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=43BF7337.7020506@domain.hid \
    --to=jim.cromie@domain.hid \
    --cc=kentborg@domain.hid \
    --cc=xenomai@xenomai.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 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.