genode-main — [INACTIVE] Genode OS framework mailing list - use https://lists.genode.org/listinfo/users

l4linux block driver bugs

[i.ismagilov <i.i...@sa...>]

Thanks for fast fixing of 'SD card doesn't start due to I/O pages
caching' bug.

But SD card still doesn't normally work on PandaBoard.

 

It seems that there are 2 more problems with it.

* *

*Bug 1.*

File cache subsystem generates an interrupt processing error _at
intensive read/write access to SD card_: in Vcpu interrupts are disabled
in the place where they should be allowed
(/ports-foc/contrib/l4linux/fs/buffer.c:1231/).

The same error occurs in qemu in other sub-system
(/ports-foc/contrib/l4linux/kernel/softirq.c:159/)

 

*Solution:*
Function prototype in /ports-foc/src/lib/l4lx/include/linux.h/:

/FASTCALL void l4x_irq_save(unsigned long *flags*);
/should be:

/FASTCALL void l4x_irq_save(unsigned long **flags*);/

So, value of interrupt state (enabling/disabling) was not properly
stored before above correction.

 

*Bug 2.*

L4Linux 'hangs' because of problem with its virtual block device _at
intensive read/write access to SD card on PandaBoard_.

 

In Genode block driver memory for storing of packages sent via IPC
sometimes is over /(ports-foc/src/lib/l4lx/genode_block.cc:281)/.

In such case L4Linux virtual block driver is blocked on semaphore
/(ports-foc/src/drivers/genode_block.c:98)/.

When memory for IPC packages storage in Genode block driver becomes
ready for use, driver sends signal to the thread '*blk-signal-thread*'
/(ports-foc/src/lib/l4lx/genode_block.cc:126)/.

Thread 'blk-signal-thread' catches the signal and generates interrupt by
calling function '*l4_irq_trigger*'
/(ports-foc/src/lib/l4lx/genode_block.cc:154)/.

But, L4Linux doesn't catch the interrupt and hangs.

In normal case interrupt is to be catched and interrupt handler
'*event_interrupt*' /(ports-foc/src/drivers/genode_block.c:172)/ should
be called; increment semaphore counter by 1
(/ports-foc/src/drivers/genode_block.c:146/) and thus un-block L4Linux
driver.

Re: Trouble porting linux driver to DDE Kit

[Norman F. <nor...@ge...>]

Hi Alexander,

> Sorry, I have not studied the whole source code yet, but I have the
> impression
> that after mapping memory via attaching mmio dataspace via rm reading
> registers by the pointer and via Register c++ template class gives
> different results.
> I had the trouble - my I2C driver from uboot didn't work when I just mapped
> the memory,
> but Ivan Loskutov has reworked it to use the Register class and it worked
> from now on.

maybe the trouble was related to the bug report we discussed yesterday? See:


http://sourceforge.net/mailarchive/forum.php?thread_name=506D7D02.2040904%40genode-labs.com&forum_name=genode-main

(you will have to click on "Attachments: Message as HTML" of the first
message)

> Could you tell if I'm digging in the correct direction? I think both IO
> memory and
> buffers must be mapped uncached, unbuffered via arm mmu, but, again, I've
> not
> yet read all the code of genode and fiasco.

You are definitely on the right track!

> If you're interested, here is what I suggest (and want to do later),
> but I'm planning to write a more detailed blog entry later and keep you
> updated.
>  * replacing most panda stuff with omap4 name
>  (i.e., move headers from include/board/panda to include/cpu/omap4)

That's a good idea. Maybe we could even think about introducing another
indirection 'soc'. ARMv7 is a 'cpu', OMAP4 is a 'soc', Pandaboard is a
'board'.

>  * Implementing abstractions for various device classes (like, gpio,
> voltage regulator,
>  led in linux, but in C++)

I agree. The corresponding session interfaces implemented by Ivan are a
good start. So far, we haven't included them in our upstream tree
because there was no pull request or topic in our issue tracker to
discuss it. If you are interested, I would appreciate you opening a new
topic for each device class. So we can take the discussion over there.

>  * splitting dde kit's common stuff (lx_emul, platform) and usb driver.
> Ideally, it should
>  be easy to add new drivers to the makefile and build each linux driver as
> a standalone binary

That is completely in line with our intentions. We planned to split
those parts into reusable pieces as soon as we reach a certain diversity
of drivers within dde_linux. Maybe, we are just reaching this point now? ;-)

Cheers
Norman

-- 
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

Re: Trouble porting linux driver to DDE Kit

[Alexander T. <ale...@gm...>]

2012/10/5 Norman Feske <nor...@ge...>

> Hi Alexander,
>
> welcome to the mailing list!
>
> After reading your email, my first intention would be to check the GPIO
> configuration of the Pandaboard.

Hi! I will recheck the GPIO configuration. I forgot to mention in the
previous
letter that I have tried stripping down linux to minimum, commenting out
all clock, gpiomux and i2c initialization, and it still worked - I assume
uboot did
enough to init it.

Sorry, I have not studied the whole source code yet, but I have the
impression
that after mapping memory via attaching mmio dataspace via rm reading
registers by the pointer and via Register c++ template class gives
different results.
I had the trouble - my I2C driver from uboot didn't work when I just mapped
the memory,
but Ivan Loskutov has reworked it to use the Register class and it worked
from now on.

Could you tell if I'm digging in the correct direction? I think both IO
memory and
buffers must be mapped uncached, unbuffered via arm mmu, but, again, I've
not
yet read all the code of genode and fiasco.


> As another note, I have the impression that OTG is actutally unrelated
> to the existing USB device driver. It is different device. Is this
> correct? If yes, wouldn't it be sensible to put the OTG driver into a
> separate driver component instead of co-locating it with the existing
> USB driver? This would avoid the complexities of the existing USB code
> when looking at the OTG issue.
>
For sure. I would like to introduce several proposals about the design of
BSP
in genode later. I want to have hardware working and then factor out common
code.

If you're interested, here is what I suggest (and want to do later),
but I'm planning to write a more detailed blog entry later and keep you
updated.
 * replacing most panda stuff with omap4 name
 (i.e., move headers from include/board/panda to include/cpu/omap4)
 * Implementing abstractions for various device classes (like, gpio,
voltage regulator,
 led in linux, but in C++)
 * splitting dde kit's common stuff (lx_emul, platform) and usb driver.
Ideally, it should
 be easy to add new drivers to the makefile and build each linux driver as
a standalone binary

-- 
Regards, Alexander

Re: Trouble porting linux driver to DDE Kit

[Norman F. <nor...@ge...>]

Hi Alexander,

welcome to the mailing list!

After reading your email, my first intention would be to check the GPIO
configuration of the Pandaboard. From page 40 of the Pandaboard manual
[1], I gather that two GPIO pins of the OMAP chip are directly connected
to the USB-OTG connector, presumably for the power supply. In your code,
I do not find the initialization of the corresponding GPIO pins 179 and
180. I expected this code to be present in
'dde_linux/src/drivers/usb/arm/platform/platform.cc'.

As another note, I have the impression that OTG is actutally unrelated
to the existing USB device driver. It is different device. Is this
correct? If yes, wouldn't it be sensible to put the OTG driver into a
separate driver component instead of co-locating it with the existing
USB driver? This would avoid the complexities of the existing USB code
when looking at the OTG issue.

[1] Pandaboard manual

http://pandaboard.org/sites/default/files/board_reference/pandaboard-es-b/panda-es-b-manual.pdf

Cheers
Norman

On 10/05/2012 01:15 PM, Alexander Tarasikov wrote:
> Hi, Genode crowd!
> 
> I've been porting the MUSB OTG driver for the OMAP4 platform to
> the Genode Framework.
> 
> I have implemented the following:
>  * some linux routines for platform devices (to manage resources)
>  * added code for some stubs in dde kit (strings, mutexes, spin locks)
>  * the I2C driver class for Genode and ported the OMAP4 I2C driver
>  * the TWL controller routines to read/write registers
>  * misc omap4 phy init (clocks and other registers)
> 
> This has allowed me to compile and run the musb driver and the
> gadget drivers (zero, ethernet) from the linux kernel. However, I've
> been desperately trying to figure out why it is not working.
> 
> I have enabled all the levels of debugging in the usb drivers and have
> dumped the MUSB FIFO in both linux and genode. The good thing is
> that the data is not all zeroes or all ones, but correct usb requests
> starting with 0x80. I think this indicates memory IO is working.
> 
> The bad thing is that under linux I get the correct usb requests
> (80 06, that is, GET_DESCRIPTOR).
> Under genode I either get SET_DESCRIPTOR or SET_ADDRESS all the
> time and the host (desktop) says "device descriptor read/64, error -32".
> 
> Does anyone have any idea what may have gone wrong? IO and register
> access seems to work so I'm lost here.
> 
> I have pushed the code to my github if you may want to try it out yourself
> git://github.com/astarasikov/genode.git
> The branch is omap4-otg-dirty. I have also pushed the 'contrib' directory
> because I was lazy to prepare the patches and fight Makefiles until the
> driver
> is working. My run script is called "panda_otg.run" (in my personal
> directory,
> astarasikov/run).
> 
> I have also made the kernel message dumps in linux and genode so
> that it's possible to compare how usb behaves. I have also disabled L2 cache
> in uboot since it caused a lot of trouble with framebuffer previously.
> 
> http://pastebin.ca/2239708
> http://pastebin.ca/2239709
> 
> Note that I have the commented out the setting up interrupts part for the
> omap4 twl. Actually, zero is returned as the default irq number which is
> timer.
> I have tested with both the correct irq number and the zero interrupt, it
> does not affect anything - in both cases the device does detect when the
> cable is plugged, but fails to set up the connection.

-- 
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

Trouble porting linux driver to DDE Kit

[Alexander T. <ale...@gm...>]

Hi, Genode crowd!

I've been porting the MUSB OTG driver for the OMAP4 platform to
the Genode Framework.

I have implemented the following:
 * some linux routines for platform devices (to manage resources)
 * added code for some stubs in dde kit (strings, mutexes, spin locks)
 * the I2C driver class for Genode and ported the OMAP4 I2C driver
 * the TWL controller routines to read/write registers
 * misc omap4 phy init (clocks and other registers)

This has allowed me to compile and run the musb driver and the
gadget drivers (zero, ethernet) from the linux kernel. However, I've
been desperately trying to figure out why it is not working.

I have enabled all the levels of debugging in the usb drivers and have
dumped the MUSB FIFO in both linux and genode. The good thing is
that the data is not all zeroes or all ones, but correct usb requests
starting with 0x80. I think this indicates memory IO is working.

The bad thing is that under linux I get the correct usb requests
(80 06, that is, GET_DESCRIPTOR).
Under genode I either get SET_DESCRIPTOR or SET_ADDRESS all the
time and the host (desktop) says "device descriptor read/64, error -32".

Does anyone have any idea what may have gone wrong? IO and register
access seems to work so I'm lost here.

I have pushed the code to my github if you may want to try it out yourself
git://github.com/astarasikov/genode.git
The branch is omap4-otg-dirty. I have also pushed the 'contrib' directory
because I was lazy to prepare the patches and fight Makefiles until the
driver
is working. My run script is called "panda_otg.run" (in my personal
directory,
astarasikov/run).

I have also made the kernel message dumps in linux and genode so
that it's possible to compare how usb behaves. I have also disabled L2 cache
in uboot since it caused a lot of trouble with framebuffer previously.

http://pastebin.ca/2239708
http://pastebin.ca/2239709

Note that I have the commented out the setting up interrupts part for the
omap4 twl. Actually, zero is returned as the default irq number which is
timer.
I have tested with both the correct irq number and the zero interrupt, it
does not affect anything - in both cases the device does detect when the
cable is plugged, but fails to set up the connection.

-- 
Regards, Alexander

Re: SD service of Genode master branch for Fiasco.OC / PandaBoard doesn’t start

[Norman F. <nor...@ge...>]

Hello,

thank your for the excellent bug report and your investigation. We could
reproduce the issue.

The root cause turned out to be somewhere else, more specifically it is
an uninitialized member variable in core's I/O-memory 'Dataspace_attr'.
With the old Fiasco.OC version, this bug did not trigger because memory
was never mapped as write combined. Revision 40 of the kernel fixes that
and consequently triggered the bug in core. The fix is available in the
master branch. Here is the patch for reference:


https://github.com/genodelabs/genode/commit/077573015574f9df5edddede9a2ad709677d60db

Thanks again!
Norman

On 10/04/2012 12:05 PM, i.ismagilov wrote:
> 
> *_Bug:_*
> 
> SD service of Genode master branch _for Fiasco.OC / PandaBoard_ doesn’t
> start with *"SD command error"* (occurs in
> /os/src/drivers/sd_card/omap4/mmchs.h/:824).
> 
> *_ _*
> 
> *_Description:_**__*
> 
> L4_FPAGE_BUFFERABLE constant (/base-foc/src/base/ipc/pager.cc/:91) is
> used to configure I/O memory region.
> 
> In *Fiasco.OC *this constant is prepared as Page::*BUFFERED*
> (/base-foc/contrib/kernel/fiasco/src/kern/arm/paging-arm.cpp/:65).
> 
> In *Fiasco.OC revision* *38* this constant is equal to *0x04* (for both
> ARMv6 and ARMv7).
> 
> In revision 40 it was changed to *0x40*.
> 
> This modification causes SD card driver error (and possible other driver
> errors) for ARMv6 and v7 architectures.
> 
> *0x04*value seems to correspond to *‘Device’ memory type* (for I/O).
> Memory pages corresponding to I/O are non-cacheable.
> 
> *0x40*value is seems for ‘Normal’ memory type. *Pages are cached* in
> this case but *this is not allowed for I/O* and causes SD card error.
> 
> *_Solutions:_*
> 
> 1)      Page::*BUFFERED* constant seems to be _used for I/O only_, not
> for RAM (currently). So, we propose to set Page::BUFFERED constant to
> 0x40 in rev. 40 as it was in rev. 38 (*see attached patch*).
> 
> 2)      If Page::BUFFERED constant is planned to use _for RAM memory
> also_, some other constant for I/O memory pages configuring and related
> workaround in Genode driver to be added.

-- 
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

SD service of Genode master branch for Fiasco.OC / PandaBoard doesn’t start

[i.ismagilov <i.i...@sa...>]

Index: genode/base-foc/contrib/kernel/fiasco/src/kern/arm/paging-arm.cpp
===================================================================
--- genode/base-foc/contrib/kernel/fiasco/src/kern/arm/paging-arm.cpp	(revision 40)
+++ genode/base-foc/contrib/kernel/fiasco/src/kern/arm/paging-arm.cpp	(working copy)
@@ -62,7 +62,7 @@
 
     // The next are ARM specific
     WRITETHROUGH = 0x08, ///< Write through cached
-    BUFFERED     = 0x40, ///< Write buffer enabled -- Normal, non-cached
+    BUFFERED     = 0x04, ///< Write buffer enabled
 
     MAX_ATTRIBS  = 0x0ffc,
     Local_page   = 0x800,

Re: [Question] Genode File/IO sync

[Christian P. <chr...@ge...>]

Hello,

from your error description alone it's hard to tell what goes wrong. Can
you perhaps send us a test program (and run script) where the loss of
file content can be observed? The file content should get flushed when
closing the file via the 'close()' function. Does your test program do that?

Regards,
Christian

On 09/27/2012 06:25 AM, 김연우 wrote:
> Dear Genode,
>
>   I'm having some trouble with the File I/O.
>
>   I implemented the File I/O test program to test the Genode. And then, I had 
> experienced a loss of file contents.
>   The root cause is my mistake that I doesn't call the fsync function at end of 
> writing. But I can't understand that the file contents is never flushed, even if 
> the application doesn't not call fsync. I assume that the file system of genode 
> doesn't not using the background flush.
>   Is it correct? And if it is right, could you tell me why genode doesn't not 
> provide the function of background flush?
>
> Best,
> Kim, Youn-woo.
>
> **
>
> **
>
> *Kim, YounWoo / M. +82-10-2565-3903*
>
> *e-Mail. yw0...@sa... <mailto:eyw...@sa...>*
>
> Engineer
>
> NextGen. OS Lab in Software R&D Center
>
> *SAMSUNG ELECTRONICS CO., LTD.*
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://ad.doubleclick.net/clk;258768047;13503038;j?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>
>
> _______________________________________________
> Genode-main mailing list
> Gen...@li...
> https://lists.sourceforge.net/lists/listinfo/genode-main

[Question] Genode File/IO sync

[김연우 <yw0...@sa...>]

<HTML><HEAD><TITLE>Samsung Enterprise Portal mySingle</TITLE>
<META content="text/html; charset=euc-kr" http-equiv=Content-Type>
<STYLE id=mysingle_style type=text/css>P {
	MARGIN-TOP: 5px; FONT-FAMILY: 굴림체, arial; MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt
}
TD {
	MARGIN-TOP: 5px; FONT-FAMILY: 굴림체, arial; MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt
}
LI {
	MARGIN-TOP: 5px; FONT-FAMILY: 굴림체, arial; MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt
}
BODY {
	LINE-HEIGHT: 1.4; MARGIN: 10px; FONT-FAMILY: 굴림체, arial; FONT-SIZE: 9pt
}
</STYLE>

<META name=GENERATOR content=ActiveSquare></HEAD>
<BODY>
<P>Dear Genode,</P>
<P>&nbsp;</P>
<P>&nbsp;I'm having some trouble with the File I/O. </P>
<P>&nbsp;I implemented&nbsp;the File I/O&nbsp;test program&nbsp;to test the Genode. And then, I had experienced a loss of file contents.&nbsp;<BR>&nbsp;The root cause is my mistake that I doesn't call the fsync function at end of writing. But I can't understand that the file contents is never flushed, even if the application doesn't not call fsync. I assume that the file system of genode doesn't not using the&nbsp;background flush.<BR>&nbsp;Is it correct? And if it is right, could you tell me why genode doesn't not provide the function of background flush?</P>
<P>&nbsp;</P>
<P>Best,<BR>Kim, Youn-woo.<BR></P>
<P>&nbsp;</P><!--SP:yw0119.kim-->
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"></SPAN></STRONG></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><IMG border=0 src="http://pds.bbs.samsung.net:4010/files/bbs/images/NOTICE/d11bbs_1002/ci-ani2[031007503993].gif" width=156 height=56 b:anchor="off" b:ra="no" b:orgtype="page"></SPAN></STRONG></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">Kim, YounWoo / <SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">M. +82-10-2565-3903</SPAN></SPAN></SPAN></STRONG></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">e-Mail. <A href="mailto:eyw...@sa...">yw0...@sa...</A></SPAN></P></SPAN></SPAN></STRONG>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><SPAN><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b; FONT-SIZE: 9pt">Engineer</SPAN></SPAN></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><SPAN><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b; FONT-SIZE: 9pt">NextGen. OS Lab in Software R&amp;D Center</SPAN></SPAN></P>
<P style="LINE-HEIGHT: 100%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">SAMSUNG ELECTRONICS CO., LTD.</SPAN></STRONG></P><!--yw0119.kim:EP-->
<P>&nbsp;</P>
<TABLE id=confidentialsignimg>
<TBODY>
<TR>
<TD NAMO_LOCK>
<P><IMG border=0 src="cid:PYM...@na..." width=520></P></TD></TR></TBODY></TABLE></BODY></HTML><img src='http://ext.samsung.net/mailcheck/SeenTimeChecker?do=eef8b63af770994e1ff80e4dc1cba75b5692f17171aeb481cbb1b24ce4f2d26c5108864b9421c5e9d4a4c133ce22e0d289fe2928b38d2252d476dc49b3e68b37db9fdddda33e82cbe4a391424e62fcf6cf878f9a26ce15a0' border=0 width=0 height=0 style='display:none'>

Re: Storage device considerations

[Sebastian S. <Seb...@ge...>]

Hi Markus,

On 09/19/2012 11:16 AM, Markus Partheymueller wrote:

> starting to discover the possibilities of using storage devices under
> genode, a few questions arised:
> 
> (1) AHCI is declared non-working on Fiasco.OC and NOVA. Is this
> planned to be resolved in the near future?

AHCI should work on Fiasco.OC and Nova by now, on bare metal one has to
use it in the same way as the USB driver by starting the 'acpi_drv'
server. Beware the driver is still in a very early stage and might break
things.

> (2) USB Storage is supporting only one device. Are there plans to extend this?

Not in the immediate future.

Greetings,

Sebastian

-- 
Sebastian Sumpf
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

Re: Storage device considerations

[Norman F. <nor...@ge...>]

Hi Markus,

I will leave the first two questions to Sebastian. Let me just cover the
third topic.

> (3) Using the part_blk service, it is possible to redirect children to
> different partitions of the same storage device. What I'm interested
> in is somehow the inverse. Is it even possible for a child to get
> access to multiple block devices? I think it is quite a limiting
> constraint if a child can only access one single storage device.

This is actually possible by using the session label. If a client opens
a new block session via the 'Block::Connection' class, the constructor
accepts an optional 'label' argument. This is a string that will be
appended to the session label of the process. For example, if Vancouver
would open a block session without specifying the argument, the session
label would be just the name of the Vancouver instance, i.e.,
"vancouver". This label is supplied to the block service, which can then
base its policy on this information. For example, the 'part_blk' service
evaluates the label to assign partitions to its clients. By supplying an
additional 'label' argument to the 'Connection' constructor, multiple
sessions with different labels can be created. Those sessions can be
differentiated by the 'part_blk' service. If specifying the label
"disk0", 'part_blk' will see the label "vancouver -> disk0".

This mechanism works for assigning different partitions of the same
'part_blk' service to different block sessions of a single program.
However, you might also want to route different block sessions to
different services. For example, to connect Vancouver's "disk0" to
partition 3 of a 'part_blk' instance, and connect Vancouver's "disk1"
directly to an USB storage driver. This is possible by referring to
label session argument in the routing policy in the configuration. For
an example, take a look at 'ports/run/noux_terminal_fs.run' and look for
the '<if-arg>' node. Here, one instance of Noux should be connected to
two different instances of terminal implementations. One terminal
session is used for the stdio the init process and another session is
used to expose a virtual character device to the Noux environment. The
routing policy looks as follows:

  <route>
    <service name="Terminal">
      <if-arg key="label" value="noux"/>
      <child name="terminal_noux"/>
    </service>
    <service name="Terminal">
      <if-arg key="label" value="noux -> noux(terminal_fs)"/>
      <child name="terminal_test"/>
    </service>
    <any-service><parent/><any-child/></any-service>
  </route>

The first route is taken only if the 'label' of the session matches
"noux". In this case, the session is routed to the 'terminal_noux'
service. Otherwise, if the label matches "noux -> noux(terminal_fs)"
(where "noux(terminal_fs)" is the part of the session label explicitly
passed to the constructor of 'Terminal::Connection'), the session is
routed to the 'terminal_test' service instead.

I hope this information is of help for building more complex scenarios.
Admittedly, the '<if-arg>' session-routing mechanism is not documented
right now because we were not quite sure whether to keep it or not.
However, it turned out to be helpful in many situations. So we will most
likely stick to it. So we should definitely add this feature to the
documentation of the init process.

Thanks for bringing up this topic.

Cheers
Norman

-- 
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

Storage device considerations

[Markus P. <ma...@kl...>]

Hi Folks,

starting to discover the possibilities of using storage devices under
genode, a few questions arised:

(1) AHCI is declared non-working on Fiasco.OC and NOVA. Is this
planned to be resolved in the near future?
(2) USB Storage is supporting only one device. Are there plans to extend this?
(3) Using the part_blk service, it is possible to redirect children to
different partitions of the same storage device. What I'm interested
in is somehow the inverse. Is it even possible for a child to get
access to multiple block devices? I think it is quite a limiting
constraint if a child can only access one single storage device.

The background for this question is of course the Vancouver port. I
was able to give the guest VM access to exactly one storage device
through the Block Session Interface of the USB service. However, as
soon as the VM is configured to use a second device, the existing
infrastructure does not allow that (or I haven't found the proper
service..).

So, I would like to open the discussion on this topic to see where the
path could lead.

Cheers,

Markus

Re: How to make rm-sessions upgradeable?

[Norman F. <nor...@ge...>]

Hi Taru,

> I'll write and submit the following patches:
> 
> 1) expand Expanding_rm_session_client to handle the necessary functions
> 2) create Expanding_cpu_session_client and the assorted fixes (I have
> this code already and just need to polish it).

that sounds good. :-)

Btw, I think that the 'Expanding_*' classes are not really elegant right
now. There is quite a bit of code duplication. Adding the case for CPU
sessions will further add repetitions.

Maybe it would be beneficial to separate the retry logic (the do loop
for executing a RPC function, upgrading the session if the function
fails in a particular way, retry after upgrade) from the actual RPC
function call? I haven't had a good idea how to do that exactly but my
basic approach would be to implement the do loop in a generic way that
takes the code for the RPC function call as functor argument. What do
you think? Would you like to give it a try?

> ps. Thanks for the patience to help with this.

You are very welcome.

Cheers
Norman

Re: nic_bridge DHCP problem

[Stefan K. <ste...@ge...>]

Hello Markus,

thank you very much for discovering the cause! Yes, you're right
parentheses make sense here ;-)

regards
Stefan

On 17.09.2012 17:31, Markus Partheymueller wrote:
> Update on that:
> 
> - The DHCP problem is solved as described here:
> https://github.com/genodelabs/genode/issues/360
> - The other problem was actually my fault.
> 
> Cheers
> 
> Markus
> 
> On 14 September 2012 16:49, Markus Partheymueller <ma...@kl...> wrote:
>> I just used a dirty hack which set the udp checksum to 0 in the
>> nic_bridge and DHCP worked. But now I can't ping the qemu gateway
>> anymore, which was possible with just using the nic_drv. tcpdump shows
>> that qemu replies, but the reply doesn't come through. It seems to me
>> that the bridging has some problems.
>>
>> On 14 September 2012 16:29, Alexander Domo <do...@ra...> wrote:
>>> I confirm this problem.
>>> Although I was using VMware, and it could only be reproduced on some physical machines, and worked perfectly on others. DHCP just didn't get through.
>>>
>>> 14.09.2012, в 16:38, Markus Partheymueller <ma...@kl...> написал(а):
>>>
>>>> Hey folks,
>>>>
>>>> I'm having some trouble with the nic_bridge provided. When using the
>>>> nic_drv as single instance, everything works fine.
>>>>
>>>> But when I replace it with the nic_bridge, the requests don't seem to
>>>> make it through. In qemu's TCP dump, I recognized a difference
>>>> regarding the DHCP broadcast:
>>>>
>>>> 13:08:25.494579 IP (tos 0x0, ttl 64, id 5118, offset 0, flags [none],
>>>> proto UDP (17), length 341)
>>>>    0.0.0.0.68 > 255.255.255.255.67: [bad udp cksum 0x9134 -> 0xd233!]
>>>> BOOTP/DHCP, Request from 02:02:02:02:02:02, length 313, xid
>>>> 0x292e1940, Flags [Broadcast] (0x8000)
>>>>          Client-Ethernet-Address 02:02:02:02:02:02
>>>>          Vendor-rfc1048 Extensions
>>>>            Magic Cookie 0x63825363
>>>>            DHCP-Message Option 53, length 1: Discover
>>>>            MSZ Option 57, length 2: 1500
>>>>            Vendor-Class Option 60, length 42:
>>>> "dhcpcd-5.2.7:Linux-3.5.0:i686:NOVA microHV"
>>>>            Hostname Option 12, length 2: "vm"
>>>>            Parameter-Request Option 55, length 15:
>>>>              Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
>>>>              Domain-Name-Server, Hostname, Domain-Name, MTU
>>>>              BR, NTP, Lease-Time, Server-ID
>>>>              RN, RB, Option 119
>>>>
>>>> The bad checksum irritated me. When I used the nic_drv session, it
>>>> worked (checksum OK, qemu's DHCP responds correctly with an IP
>>>> address). Could there be a problem with the bridge itself or is it
>>>> definitely my problem? Do you have example setups using the bridge
>>>> that work?
>>>>
>>>> Best,
>>>>
>>>> Markus
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Got visibility?
>>>> Most devs has no idea what their production app looks like.
>>>> Find out how fast your code is with AppDynamics Lite.
>>>> http://ad.doubleclick.net/clk;262219671;13503038;y?
>>>> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>>>> _______________________________________________
>>>> Genode-main mailing list
>>>> Gen...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/genode-main
>>>
>>> ------------------------------------------------------------------------------
>>> Got visibility?
>>> Most devs has no idea what their production app looks like.
>>> Find out how fast your code is with AppDynamics Lite.
>>> http://ad.doubleclick.net/clk;262219671;13503038;y?
>>> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>>> _______________________________________________
>>> Genode-main mailing list
>>> Gen...@li...
>>> https://lists.sourceforge.net/lists/listinfo/genode-main
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Genode-main mailing list
> Gen...@li...
> https://lists.sourceforge.net/lists/listinfo/genode-main
> 

-- 
Stefan Kalkowski
Genode Labs

http://www.genode-labs.com/ · http://genode.org/

Re: nic_bridge DHCP problem

[Markus P. <ma...@kl...>]

Update on that:

- The DHCP problem is solved as described here:
https://github.com/genodelabs/genode/issues/360
- The other problem was actually my fault.

Cheers

Markus

On 14 September 2012 16:49, Markus Partheymueller <ma...@kl...> wrote:
> I just used a dirty hack which set the udp checksum to 0 in the
> nic_bridge and DHCP worked. But now I can't ping the qemu gateway
> anymore, which was possible with just using the nic_drv. tcpdump shows
> that qemu replies, but the reply doesn't come through. It seems to me
> that the bridging has some problems.
>
> On 14 September 2012 16:29, Alexander Domo <do...@ra...> wrote:
>> I confirm this problem.
>> Although I was using VMware, and it could only be reproduced on some physical machines, and worked perfectly on others. DHCP just didn't get through.
>>
>> 14.09.2012, в 16:38, Markus Partheymueller <ma...@kl...> написал(а):
>>
>>> Hey folks,
>>>
>>> I'm having some trouble with the nic_bridge provided. When using the
>>> nic_drv as single instance, everything works fine.
>>>
>>> But when I replace it with the nic_bridge, the requests don't seem to
>>> make it through. In qemu's TCP dump, I recognized a difference
>>> regarding the DHCP broadcast:
>>>
>>> 13:08:25.494579 IP (tos 0x0, ttl 64, id 5118, offset 0, flags [none],
>>> proto UDP (17), length 341)
>>>    0.0.0.0.68 > 255.255.255.255.67: [bad udp cksum 0x9134 -> 0xd233!]
>>> BOOTP/DHCP, Request from 02:02:02:02:02:02, length 313, xid
>>> 0x292e1940, Flags [Broadcast] (0x8000)
>>>          Client-Ethernet-Address 02:02:02:02:02:02
>>>          Vendor-rfc1048 Extensions
>>>            Magic Cookie 0x63825363
>>>            DHCP-Message Option 53, length 1: Discover
>>>            MSZ Option 57, length 2: 1500
>>>            Vendor-Class Option 60, length 42:
>>> "dhcpcd-5.2.7:Linux-3.5.0:i686:NOVA microHV"
>>>            Hostname Option 12, length 2: "vm"
>>>            Parameter-Request Option 55, length 15:
>>>              Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
>>>              Domain-Name-Server, Hostname, Domain-Name, MTU
>>>              BR, NTP, Lease-Time, Server-ID
>>>              RN, RB, Option 119
>>>
>>> The bad checksum irritated me. When I used the nic_drv session, it
>>> worked (checksum OK, qemu's DHCP responds correctly with an IP
>>> address). Could there be a problem with the bridge itself or is it
>>> definitely my problem? Do you have example setups using the bridge
>>> that work?
>>>
>>> Best,
>>>
>>> Markus
>>>
>>> ------------------------------------------------------------------------------
>>> Got visibility?
>>> Most devs has no idea what their production app looks like.
>>> Find out how fast your code is with AppDynamics Lite.
>>> http://ad.doubleclick.net/clk;262219671;13503038;y?
>>> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>>> _______________________________________________
>>> Genode-main mailing list
>>> Gen...@li...
>>> https://lists.sourceforge.net/lists/listinfo/genode-main
>>
>> ------------------------------------------------------------------------------
>> Got visibility?
>> Most devs has no idea what their production app looks like.
>> Find out how fast your code is with AppDynamics Lite.
>> http://ad.doubleclick.net/clk;262219671;13503038;y?
>> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>> _______________________________________________
>> Genode-main mailing list
>> Gen...@li...
>> https://lists.sourceforge.net/lists/listinfo/genode-main

Re: Qt and lwip-1.4.1

[J. S. <jso...@go...>]

Hello Ivan,

On 09/17/2012 12:05 PM, Ivan Loskutov wrote:
> *After upgrade lwip to version 1.4.1 I have an issue in qt-network. In my
> fork was implemented Ssl support in qt-network for using in web browsers.
> With new lwip https doesn’t work. Http works, but I think with issues too.

Tbh, I only tested HTTPS support in noux-pkg/lynx which works fine but I
will take a look at SSL support in QtNetwork.

> I tried to investigate this issue. I think it is related to non-blocking
> sockets, which implemented in the new version. All simple examples are
> working properly. Issues occur only in a Qt application. I found that
> qtapplication calls connect and the connection started in non-blocking
 > mode, connect return EINPROGRESS. After qt made call connect again,
 > in such case connect must return EAGAIN, but it doesn’thappen in lwip.
> It doesn’t affect for http connection, but ssl connection is dropped.
> Anyone already faced such issues?*

Unfortunatly lwip does not support these errno value. It always returns
EALREADY even if the connection was already established. So we changed
this to EISCONN - which works fine for arora, because there is no code
in lwip that handles the various steps of a non-blocking connect() in
the socket-api (e.g. EAGAIN). That means you will get EINPROGRESS while 
lwip is connecting and EISCONN when it connected succuessfully.


Regards, Josef

Qt and lwip-1.4.1

[Ivan L. <los...@gm...>]

*After upgrade lwip to version 1.4.1 I have an issue in qt-network. In my
fork was implemented Ssl support in qt-network for using in web browsers.
With new lwip https doesn’t work. Http works, but I think with issues too.
I tried to investigate this issue. I think it is related to non-blocking
sockets, which implemented in the new version. All simple examples are
working properly. Issues occur only in a Qt application. I found that
qtapplication calls
connect and the connection started in non-blocking mode, connect return
EINPROGRESS. After qt made call connect again, in such case connect must
return EAGAIN, but it doesn’t  happen in lwip. It doesn’t affect for http
connection, but ssl connection is dropped.
Anyone already faced such issues?*

--
Ivan Loskutov

Re: How to make rm-sessions upgradeable?

[Taru K. <ta...@ta...>]

On Sun, 16 Sep 2012 12:36:48 +0200, Norman Feske <nor...@ge...> wrote:
> there is already a bit of support for such upgrades in place. Please
> have a look at 'base/include/base/platform_env.h'. The class behind
> 'env()->rm_session()' is actually an 'Expanding_rm_session_client',
> which is meant to transparently upgrade the session quota as needed.
> Right now, the implementation covers only the 'attach' function though.
> For accommodating your concern, we should cover all functions that
> implicitly consume session quota. In your actual case, this would be
> 'add_client'.

Thanks. I was aware of the Expanding_*_client classes but I was mistaken
in the belief that the thread creation used rm in some implicit way
instead of going through that session. My mistake.

I'll write and submit the following patches:

1) expand Expanding_rm_session_client to handle the necessary functions
2) create Expanding_cpu_session_client and the assorted fixes (I have
this code already and just need to polish it).

ps. Thanks for the patience to help with this.

- Taru Karttunen

Re: How to make rm-sessions upgradeable?

[Norman F. <nor...@ge...>]

Hi Taru,

> When spawning more threads the rm-session from the env needs to be
> upgraded in various places. This can occur when spawning new threads and
> even in thread.start().
> 
> Thus one needs a way to make the rm-session in env upgradeable from the
> outside.

there is already a bit of support for such upgrades in place. Please
have a look at 'base/include/base/platform_env.h'. The class behind
'env()->rm_session()' is actually an 'Expanding_rm_session_client',
which is meant to transparently upgrade the session quota as needed.
Right now, the implementation covers only the 'attach' function though.
For accommodating your concern, we should cover all functions that
implicitly consume session quota. In your actual case, this would be
'add_client'.

> A simple way to fix would be to define a
> class Upgradeable_rm_session : public Rm_session {
>       void upgrade(const char *);
> };

The 'Platform_env::Expanding_rm_session' class looks actually quite
similar. Could you have look to see how it fits your needs?

> And make some private inheritance into protected inheritance 
> i.e. Rpc_client into
> template <typename RPC_INTERFACE>
> struct Rpc_client : *protected* Capability<RPC_INTERFACE>, RPC_INTERFACE
> ...

Oh, you have just turned a public inheritance into a protected one. ;-)
If a 'struct' inherits a base class with no 'private/protected/public'
keyword, 'public' is default.

Cheers
Norman

-- 
Dr.-Ing. Norman Feske
Genode Labs

http://www.genode-labs.com · http://genode.org

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

How to make rm-sessions upgradeable?

[Taru K. <ta...@ta...>]

Hello

When spawning more threads the rm-session from the env needs to be
upgraded in various places. This can occur when spawning new threads and
even in thread.start().

Thus one needs a way to make the rm-session in env upgradeable from the
outside.

A simple way to fix would be to define a
class Upgradeable_rm_session : public Rm_session {
      void upgrade(const char *);
};

And make some private inheritance into protected inheritance 
i.e. Rpc_client into
template <typename RPC_INTERFACE>
struct Rpc_client : *protected* Capability<RPC_INTERFACE>, RPC_INTERFACE
...

Is there a better and more non-invasive way to do this?

If not - would a patch implementing this be accepted?

An alternative would be to expose the capability in env in addition to
the session, but I think that is even more ugly.

- Taru Karttunen

Re: nic_bridge DHCP problem

[Markus P. <ma...@kl...>]

I just used a dirty hack which set the udp checksum to 0 in the
nic_bridge and DHCP worked. But now I can't ping the qemu gateway
anymore, which was possible with just using the nic_drv. tcpdump shows
that qemu replies, but the reply doesn't come through. It seems to me
that the bridging has some problems.

On 14 September 2012 16:29, Alexander Domo <do...@ra...> wrote:
> I confirm this problem.
> Although I was using VMware, and it could only be reproduced on some physical machines, and worked perfectly on others. DHCP just didn't get through.
>
> 14.09.2012, в 16:38, Markus Partheymueller <ma...@kl...> написал(а):
>
>> Hey folks,
>>
>> I'm having some trouble with the nic_bridge provided. When using the
>> nic_drv as single instance, everything works fine.
>>
>> But when I replace it with the nic_bridge, the requests don't seem to
>> make it through. In qemu's TCP dump, I recognized a difference
>> regarding the DHCP broadcast:
>>
>> 13:08:25.494579 IP (tos 0x0, ttl 64, id 5118, offset 0, flags [none],
>> proto UDP (17), length 341)
>>    0.0.0.0.68 > 255.255.255.255.67: [bad udp cksum 0x9134 -> 0xd233!]
>> BOOTP/DHCP, Request from 02:02:02:02:02:02, length 313, xid
>> 0x292e1940, Flags [Broadcast] (0x8000)
>>          Client-Ethernet-Address 02:02:02:02:02:02
>>          Vendor-rfc1048 Extensions
>>            Magic Cookie 0x63825363
>>            DHCP-Message Option 53, length 1: Discover
>>            MSZ Option 57, length 2: 1500
>>            Vendor-Class Option 60, length 42:
>> "dhcpcd-5.2.7:Linux-3.5.0:i686:NOVA microHV"
>>            Hostname Option 12, length 2: "vm"
>>            Parameter-Request Option 55, length 15:
>>              Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
>>              Domain-Name-Server, Hostname, Domain-Name, MTU
>>              BR, NTP, Lease-Time, Server-ID
>>              RN, RB, Option 119
>>
>> The bad checksum irritated me. When I used the nic_drv session, it
>> worked (checksum OK, qemu's DHCP responds correctly with an IP
>> address). Could there be a problem with the bridge itself or is it
>> definitely my problem? Do you have example setups using the bridge
>> that work?
>>
>> Best,
>>
>> Markus
>>
>> ------------------------------------------------------------------------------
>> Got visibility?
>> Most devs has no idea what their production app looks like.
>> Find out how fast your code is with AppDynamics Lite.
>> http://ad.doubleclick.net/clk;262219671;13503038;y?
>> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>> _______________________________________________
>> Genode-main mailing list
>> Gen...@li...
>> https://lists.sourceforge.net/lists/listinfo/genode-main
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Genode-main mailing list
> Gen...@li...
> https://lists.sourceforge.net/lists/listinfo/genode-main

Re: nic_bridge DHCP problem

[Alexander D. <do...@ra...>]

I confirm this problem.
Although I was using VMware, and it could only be reproduced on some physical machines, and worked perfectly on others. DHCP just didn't get through.

14.09.2012, в 16:38, Markus Partheymueller <ma...@kl...> написал(а):

> Hey folks,
> 
> I'm having some trouble with the nic_bridge provided. When using the
> nic_drv as single instance, everything works fine.
> 
> But when I replace it with the nic_bridge, the requests don't seem to
> make it through. In qemu's TCP dump, I recognized a difference
> regarding the DHCP broadcast:
> 
> 13:08:25.494579 IP (tos 0x0, ttl 64, id 5118, offset 0, flags [none],
> proto UDP (17), length 341)
>    0.0.0.0.68 > 255.255.255.255.67: [bad udp cksum 0x9134 -> 0xd233!]
> BOOTP/DHCP, Request from 02:02:02:02:02:02, length 313, xid
> 0x292e1940, Flags [Broadcast] (0x8000)
>          Client-Ethernet-Address 02:02:02:02:02:02
>          Vendor-rfc1048 Extensions
>            Magic Cookie 0x63825363
>            DHCP-Message Option 53, length 1: Discover
>            MSZ Option 57, length 2: 1500
>            Vendor-Class Option 60, length 42:
> "dhcpcd-5.2.7:Linux-3.5.0:i686:NOVA microHV"
>            Hostname Option 12, length 2: "vm"
>            Parameter-Request Option 55, length 15:
>              Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
>              Domain-Name-Server, Hostname, Domain-Name, MTU
>              BR, NTP, Lease-Time, Server-ID
>              RN, RB, Option 119
> 
> The bad checksum irritated me. When I used the nic_drv session, it
> worked (checksum OK, qemu's DHCP responds correctly with an IP
> address). Could there be a problem with the bridge itself or is it
> definitely my problem? Do you have example setups using the bridge
> that work?
> 
> Best,
> 
> Markus
> 
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Genode-main mailing list
> Gen...@li...
> https://lists.sourceforge.net/lists/listinfo/genode-main

nic_bridge DHCP problem

[Markus P. <ma...@kl...>]

Hey folks,

I'm having some trouble with the nic_bridge provided. When using the
nic_drv as single instance, everything works fine.

But when I replace it with the nic_bridge, the requests don't seem to
make it through. In qemu's TCP dump, I recognized a difference
regarding the DHCP broadcast:

13:08:25.494579 IP (tos 0x0, ttl 64, id 5118, offset 0, flags [none],
proto UDP (17), length 341)
    0.0.0.0.68 > 255.255.255.255.67: [bad udp cksum 0x9134 -> 0xd233!]
BOOTP/DHCP, Request from 02:02:02:02:02:02, length 313, xid
0x292e1940, Flags [Broadcast] (0x8000)
          Client-Ethernet-Address 02:02:02:02:02:02
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            MSZ Option 57, length 2: 1500
            Vendor-Class Option 60, length 42:
"dhcpcd-5.2.7:Linux-3.5.0:i686:NOVA microHV"
            Hostname Option 12, length 2: "vm"
            Parameter-Request Option 55, length 15:
              Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
              Domain-Name-Server, Hostname, Domain-Name, MTU
              BR, NTP, Lease-Time, Server-ID
              RN, RB, Option 119

The bad checksum irritated me. When I used the nic_drv session, it
worked (checksum OK, qemu's DHCP responds correctly with an IP
address). Could there be a problem with the bridge itself or is it
definitely my problem? Do you have example setups using the bridge
that work?

Best,

Markus

Re: [Error report] f_stat() failed with error code FR_NO_FILE

[Christian P. <chr...@ge...>]

Hello,

I created a new issue for this problem in our bug tracker (https://github.com/genodelabs/genode/issues/355), including a patch:
https://github.com/cproc/genode/commit/d44104bfbaf12e2c1b0500a101a56e6c5f0e0dff.patch

Christian

[Error report] f_stat() failed with error code FR_NO_FILE

[김은석 <eun...@sa...>]

<HTML><HEAD><TITLE>Samsung Enterprise Portal mySingle</TITLE>
<META content="text/html; charset=euc-kr" http-equiv=Content-Type>
<STYLE id=mysingle_style type=text/css>P {
	MARGIN-TOP: 5px; FONT-FAMILY: 굴림체, arial; MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt
}
TD {
	MARGIN-TOP: 5px; FONT-FAMILY: 굴림체, arial; MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt
}
LI {
	MARGIN-TOP: 5px; FONT-FAMILY: 굴림체, arial; MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt
}
BODY {
	LINE-HEIGHT: 1.4; MARGIN: 10px; FONT-FAMILY: 굴림체, arial; FONT-SIZE: 9pt
}
</STYLE>

<META name=GENERATOR content=ActiveSquare></HEAD>
<BODY>
<P>Dear Genode ..</P>
<P>&nbsp;</P>
<P>I wanna open and read&nbsp;a file "/localfs/xxxxds_on_genode2CB68EFD" by using the open() function and pread() function on the Panda_Board.</P>
<P>However, I can't read the file when i used the pread() function because of following error.</P>
<P>&nbsp;</P>
<P>"f_stat() failed with error code FR_NO_FILE"</P>
<P>&nbsp;</P>
<P>Could you please tell me how to solve this problem.</P>
<P>Please take a look, Thank you.</P>
<P>Best regards,</P>
<P>Eunseok, Kim.</P>
<P>&nbsp;</P>
<P>&nbsp;</P><!--SP:eunseok.kim-->
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"></SPAN></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><IMG style="WIDTH: 156px; HEIGHT: 56px; TEXT-DECORATION: " title=삼성로고 border=0 alt=삼성로고 src="cid:44Y...@na..."></SPAN></STRONG></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">EunSeok&nbsp;Kim /&nbsp;<SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">M. +82-10-9035-7096</SPAN></SPAN></SPAN></STRONG></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b"><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">e-Mail. <A href="mailto:eun...@sa...">eun...@sa...</A></SPAN></P></SPAN></SPAN></STRONG>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><SPAN><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b; FONT-SIZE: 9pt">Assistant Engineer</SPAN></SPAN></P>
<P style="LINE-HEIGHT: 120%; MARGIN-BOTTOM: 0px"><SPAN><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b; FONT-SIZE: 9pt">NextGen. OS&nbsp;Lab in Software R&amp;D Center</SPAN></SPAN></P>
<P style="LINE-HEIGHT: 100%; MARGIN-BOTTOM: 0px"><STRONG><SPAN style="FONT-FAMILY: 맑은 고딕; COLOR: #00008b">SAMSUNG ELECTRONICS CO., LTD.</SPAN></STRONG></P><!--youth.kim:EP--><!--eunseok.kim:EP-->
<P>&nbsp;</P>
<TABLE id=confidentialsignimg>
<TBODY>
<TR>
<TD NAMO_LOCK>
<P><IMG border=0 src="cid:7EU...@na..." width=520></P></TD></TR></TBODY></TABLE></BODY></HTML><img src='http://ext.samsung.net/mailcheck/SeenTimeChecker?do=245c6227ec1d438fcbdc1901fd65397fc4d28b25906e4f92a61375b0ae6314f29ba4f25794b1084bd1afaaba7860cdcd8048f33cf1ed6b02263067d8b8f027b11b20909a04efd4d2748cfe1d4e847419cf878f9a26ce15a0' border=0 width=0 height=0 style='display:none'>