build error after selecting POSIX interface,
on svn-head - ie 515
[EMAIL PROTECTED] linux-2.6.15.1-ipipe-103-sonyI]$ make
CHK include/linux/version.h
SPLIT include/linux/autoconf.h -> include/config/*
CHK include/linux/compile.h
CHK usr/initramfs_list
CC [M] kernel/xenomai/skins/posix/sched.o
In
some random sucesses ..
Ive been running an ipipe kernel as the default since shortly after 1/7.
Since then, Ive had a couple of freezes on boot,
and sometimes bash's auto-complete takes longer to complete,
but other than that, things have been solid.
But that kernel wasnt configured using scri
Philippe Gerum wrote:
Ive been running an ipipe kernel as the default since shortly after 1/7.
Since then, Ive had a couple of freezes on boot,
and sometimes bash's auto-complete takes longer to complete,
Eh? Maybe the CONFIG_PCI_MSI syndrom again?
Um, does this tell you anything ?
$ zcat
Hi Jim,
Jim Cromie wrote:
some random sucesses ..
Ive been running an ipipe kernel as the default since shortly after 1/7.
Since then, Ive had a couple of freezes on boot,
and sometimes bash's auto-complete takes longer to complete,
Eh? Maybe the CONFIG_PCI_MSI syndrom again?
but other th
some random sucesses ..
Ive been running an ipipe kernel as the default since shortly after 1/7.
Since then, Ive had a couple of freezes on boot,
and sometimes bash's auto-complete takes longer to complete,
but other than that, things have been solid.
But that kernel wasnt configured using scri
build error after selecting POSIX interface,
on svn-head - ie 515
[EMAIL PROTECTED] linux-2.6.15.1-ipipe-103-sonyI]$ make
CHK include/linux/version.h
SPLIT include/linux/autoconf.h -> include/config/*
CHK include/linux/compile.h
CHK usr/initramfs_list
CC [M] kernel/xenomai/skins/posix/sched.o
In
Wolfgang Grandegger wrote:
Gilles Chanteperdrix wrote:
Wolfgang Grandegger wrote:
> Therefore we need a dedicated function to re-enable interrupts in
the > ISR. We could name it *_end_irq, but maybe *_enable_isr_irq is
more > obvious. On non-PPC archs it would translate to *_irq_enable.
I
On 02/02/06, Jan Kiszka <[EMAIL PROTECTED]> wrote:
Dmitry Adamushko wrote:> Hi there,>> as I promised, here go the following patches (ordered as they have to be> applied one by one) :>>> 1) shirq-base.patch>> Adds the "name" field to the interrupt object of the nucleus layer.
> Reworks the related
Dmitry Adamushko wrote:
> Hi there,
>
> as I promised, here go the following patches (ordered as they have to be
> applied one by one) :
>
>
> 1) shirq-base.patch
>
> Adds the "name" field to the interrupt object of the nucleus layer.
> Reworks the related bits of the native skin (+ a few minor
Wolfgang Grandegger wrote:
Gilles Chanteperdrix wrote:
Wolfgang Grandegger wrote:
> Therefore we need a dedicated function to re-enable interrupts in
the > ISR. We could name it *_end_irq, but maybe *_enable_isr_irq is
more > obvious. On non-PPC archs it would translate to *_irq_enable.
I
On 02/02/06, Jan Kiszka <[EMAIL PROTECTED]> wrote:
Dmitry Adamushko wrote:> Hi there,>> as I promised, here go the following patches (ordered as they have to be> applied one by one) :>>> 1) shirq-base.patch>> Adds the "name" field to the interrupt object of the nucleus layer.
> Reworks the related
Dmitry Adamushko wrote:
> Hi there,
>
> as I promised, here go the following patches (ordered as they have to be
> applied one by one) :
>
>
> 1) shirq-base.patch
>
> Adds the "name" field to the interrupt object of the nucleus layer.
> Reworks the related bits of the native skin (+ a few minor
12 matches
Mail list logo