On 11/28/18 7:56 AM, Jan Kiszka wrote:
> On 27.11.18 19:54, Philippe Gerum wrote:
>> On 11/27/18 6:44 PM, Jan Kiszka wrote:
>>> On 08.11.18 14:24, Philippe Gerum wrote:
On 11/8/18 2:14 PM, Jan Kiszka wrote:
> On 08.11.18 14:05, Philippe Gerum wrote:
>> On 11/5/18 1:20 PM, Jan Kiszka
Hello,
Xenomai version - 3.0.5
Build-in RTnet kernel module - rt_e1000e
lspci -knn:
* Ethernet Controller [0280] Intel Corporation Device [8086:24fd] (rev 02==78)
* *Subsystem: Lenovo Ethernet Connection (2) I219-LM [17aa:310b]**
Kernel modules: e1000e*
The rt_e1000e is not listed as a module.
Am Fri, 16 Nov 2018 07:28:51 +0100
schrieb Jan Kiszka :
> On 08.11.18 13:42, Henning Schild via Xenomai wrote:
> > xeno-test-run always returned SUCCESS, even if its children exited
> > with non zero. So xeno-test can not be used programmatically i.e.
> > in CI.
> >
> > This patch adds some more
On 28.11.18 09:58, Philippe Gerum wrote:
On 11/28/18 7:56 AM, Jan Kiszka wrote:
On 27.11.18 19:54, Philippe Gerum wrote:
On 11/27/18 6:44 PM, Jan Kiszka wrote:
On 08.11.18 14:24, Philippe Gerum wrote:
On 11/8/18 2:14 PM, Jan Kiszka wrote:
On 08.11.18 14:05, Philippe Gerum wrote:
On 11/5/18
As I can see, the existed rt_e1000e driver didn't support the I219
device, the latest supported device is I218 devices. And I am working on
porting the newer driver now.
On 11/28/18 4:35 PM, Sakshi Bansal via Xenomai wrote:
Hello,
Xenomai version - 3.0.5
Build-in RTnet kernel module -
On 28.11.18 10:05, Henning Schild wrote:
Am Fri, 16 Nov 2018 07:28:51 +0100
schrieb Jan Kiszka :
On 08.11.18 13:42, Henning Schild via Xenomai wrote:
xeno-test-run always returned SUCCESS, even if its children exited
with non zero. So xeno-test can not be used programmatically i.e.
in CI.
Hi.
I'm porting the 3.1-dev xenomai on the ZynqMP.
I succeed build from petalinux but a WARNING message occurred on the dmesg,
like below.
[1.325926] [ cut here ]
[1.325954] WARNING: CPU: 1 PID: 1 at /kernel-source//kernel/irq/chip.c:57
irq_set_chip+0x94/0xa8
[
On 28.11.18 13:40, Josef Holzmayr wrote:
Hi Jan,
On Mon, Nov 26, 2018 at 03:40:38PM +0100, Jan Kiszka wrote:
On 26.11.18 15:30, Josef Holzmayr wrote:
On Fri, Nov 23, 2018 at 01:48:27PM +0100, Jan Kiszka wrote:
On 23.11.18 13:27, Josef Holzmayr via Xenomai wrote:
- only one BSP layer so far,
Hi,
What is the problem with "rt_queue_create" in the below code:
static size_t def_mem_pool_size = 1024 * 1024;
int libalchemy_func(void)
{
RT_QUEUE queue;
int ret=0;
printf("%s called..\n", __func__);
// ret = rt_queue_create(, "q0", def_mem_pool_size,
//
Hi Jan,
On Mon, Nov 26, 2018 at 03:40:38PM +0100, Jan Kiszka wrote:
> On 26.11.18 15:30, Josef Holzmayr wrote:
> > On Fri, Nov 23, 2018 at 01:48:27PM +0100, Jan Kiszka wrote:
> > > On 23.11.18 13:27, Josef Holzmayr via Xenomai wrote:
> > > > - only one BSP layer so far, namely the Beaglebone.
From: Jan Kiszka
This helps users that may still expect it to exist. One example is
buildroot.
While at it, remove the now unused SUDO variable.
Signed-off-by: Jan Kiszka
---
Makefile.am | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Makefile.am b/Makefile.am
index
On 28.11.18 15:42, Jan Kiszka wrote:
> On 28.11.18 13:40, Josef Holzmayr wrote:
>> Digging deeper, I now have a couple of questions. xeno-test gives me
>>
>> net_packet_dgram skipped (no kernel support)
>> net_packet_raw skipped (no kernel support)
>> net_udp skipped (no kernel support)
>
> That
12 matches
Mail list logo
