Hi Philipp,
Regarding the PCI bus issue (hardware pass-through of PCIe devices on arm64
is not yet supporting MSI-X)
Is there a method to make the device tree node of the PCIe host bridge
device for uvmm uses the Legacy IRQ instead of MSI-X ?
I tried to just remove the msi-map property from the device tree node of
the PCIe host bridge device but nothing changed!
Is there more configuration/changes should be added ?

Thanks in advance,
Regards


On Sun, Oct 27, 2024 at 11:34 AM Mohamed Dawod <[email protected]>
wrote:

>
> Hi Philipp,
> I wrote it correctly, "earlyprintk" instead of "earlyprinkt".
> but nothing changed.
>
>
> On Thu, Oct 24, 2024 at 3:20 PM Philipp Eppelt <
> [email protected]> wrote:
>
>> Hi Mohamed,
>>
>> just a quick reply. Long one comes later.
>>
>> Am 24.10.24 um 12:47 schrieb Mohamed Dawod:
>> > Hi Philipp,
>> >
>> > The mentioned commit didn't help.
>> > Also the added qemu configuration didn't change anything.
>> > I added `earlyprinkt=serial,ttyS0` in order to show more logs from the
>> VM kernel
>> Sorry, I mistyped: the linux cmdline argument is
>> `earlyprintk=serial,ttyS0`.
>> (not earlyprinkt).
>>
>>
>> Cheers,
>> Philipp
>>
>>
>> > but nothing new.
>> >
>> > I also think that it's an interrupt issue!
>> > I'm not an expert in device tree nodes, How can I use Legacy IRQ
>> instead of MSI-X ?
>> >
>> > Thanks,
>> > Regards
>> >
>> > On Wed, Oct 23, 2024 at 5:34 PM Philipp Eppelt <
>> [email protected]
>> > <mailto:[email protected]>> wrote:
>> >
>> >     Hi Mohamed,
>> >
>> >     I'm not quite certain where this issue comes from. My hunch is,
>> it's an
>> >     interrupt issue. Please try to cherry-pick this commit [1] to uvmm
>> and see if
>> >     this helps. The commit is new and probably not part of the snapshot.
>> >
>> >     Another thing is that you configured qemu to use legacy virtio
>> devices. Please
>> >     add `disable-legacy=on,disable-modern=off` to -device
>> virtio-blk-pci,...
>> >
>> >
>> >     Also note, that hardware pass-through of PCIe devices on arm64 is
>> not yet
>> >     supporting MSI-X. Meaning, the device tree node of the PCIe host
>> bridge device
>> >     for uvmm should not mention the msi-map property. Legacy IRQ should
>> work,
>> >     though.
>> >
>> >
>> >     Hint: add `earlyprinkt=serial,ttyS0` to the guest linux' command
>> line to see
>> >     more information from the guest linux boot.
>> >
>> >
>> >     Let's see what these things change.
>> >
>> >     Cheers,
>> >     Philipp
>> >
>> >
>> >
>> >     [1]
>> >
>> https://github.com/kernkonzept/uvmm/commit/b8bcbf4d34460cc7d66dcdcb7763fc1e84dbae82
>> <
>> https://github.com/kernkonzept/uvmm/commit/b8bcbf4d34460cc7d66dcdcb7763fc1e84dbae82
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >     Am 23.10.24 um 11:52 schrieb Mohamed Dawod:
>> >      > Hi,
>> >      >
>> >      > Thanks Philipp for your patience and valuable support.
>> >      >
>> >      > I changed the areas where the RAM should be placed in the memory
>> node of the
>> >      > device tree and it worked.
>> >      > Now, I want to test the pci bus by connecting a virtio-blk-pci
>> device via
>> >     qemu
>> >      > to be mounted on /dev/vda
>> >      > to do that, I run qemu using the following options :
>> >      >
>> >      >     /$ qemu-system-aarch64 -kernel
>> >      >
>> >
>>  
>> /home/dawod/workspace/l4re-snapshot-24.08.0/build_aarch64/l4/images/l4re_VM-basic-pci.elf
>> -serial stdio -M virt,virtualization=true,iommu=smmuv3 -cpu cortex-a57 -m
>> 4096 --display none *-drive
>> if=none,file=/home/dawod/storage/disk.rootfs.ext4,format=raw,id=disk0
>> -device virtio-blk-pci,drive=disk0*/
>> >      >
>> >      >
>> >      > but the VM hangs in the booting stage while trying to create the
>> /dev/vda
>> >     block
>> >      > device which will be responsible for handling the added disk.
>> >      > *please* *find attached a text log from the serial console * :
>> >      > vm-blk-pci.log
>> >      >
>> >      >
>> >     <
>> https://mail.google.com/mail/u/0?ui=2&ik=b05e32a9ef&attid=0.1&permmsgid=msg-a:r-4942377897740831663&view=att&disp=safe&realattid=f_m2lp0t191
>> <
>> https://mail.google.com/mail/u/0?ui=2&ik=b05e32a9ef&attid=0.1&permmsgid=msg-a:r-4942377897740831663&view=att&disp=safe&realattid=f_m2lp0t191
>> >>
>> >      >
>> >      > image.png
>> >      >
>> >      >
>> >      > Many Thanks,
>> >      > Regards
>> >      >
>> >      >
>> >      >
>> >      > On Tue, Oct 22, 2024 at 6:54 PM Philipp Eppelt
>> >     <[email protected] <mailto:
>> [email protected]>
>> >      > <mailto:[email protected]
>> >     <mailto:[email protected]>>> wrote:
>> >      >
>> >      >     Hi Mohamed,
>> >      >
>> >      >     I'm happy to see you resolved the issue.
>> >      >     If possible, please prefer a text log from the serial
>> console over a
>> >     picture,
>> >      >     because the text log is longer and thus provides more
>> information
>> >     about the
>> >      >     booted system.
>> >      >
>> >      >     uvmm show this error, when memory regions overlap. In this
>> case RAM
>> >     and the
>> >      >     intc
>> >      >     device overlap. The intc device is specified in the device
>> tree you
>> >     passed
>> >      >     to uvmm.
>> >      >     Here, the device tree does not contain explicit RAM regions,
>> so uvmm
>> >     sets up
>> >      >     the
>> >      >     default RAM region, which spans the area starting at zero up
>> to the
>> >     size of the
>> >      >     RAM you configured in the ned script.
>> >      >     In this case, RAM covers the area [      0: fff'ffff]
>> (256MB).
>> >      >     The itc device wants to allocate the area [0x0800'0000 :
>> 0x0800'ffff]
>> >     which is
>> >      >     contained within the already existing RAM allocation. Thus
>> the error
>> >     message.
>> >      >
>> >      >     You have two options, either specify the areas where the RAM
>> should be
>> >      >     placed in
>> >      >     the memory node of the device tree or move the intc device
>> such that
>> >     it doesn't
>> >      >     overlap. For this setup this means above 0x1000'0000.
>> >      >
>> >      >
>> >      >     Cheers
>> >      >     Philipp
>> >      >
>> >      >
>> >      >     Am 22.10.24 um 09:36 schrieb Mohamed Dawod:
>> >      >      > I upgraded L4 version to 24.08 instead of 23.10 because
>> 24.08
>> >     contains the
>> >      >      > missing virt-arm_virt-64_pci.dts file.
>> >      >      > I'm building for arm64 and when I run the demo
>> VM-basic-pci, I got the
>> >      >     following
>> >      >      > error !
>> >      >      > I didn't change anything in the dts/dtb or ned scripts
>> excepting
>> >     the typo of
>> >      >      >
>> >      >      >       overlay = "-drom/virt-pci.dtbo"
>> >      >      >
>> >      >      >
>> >      >      > What is the problem here ?
>> >      >      >
>> >      >      > image.png
>> >      >      >
>> >      >      > On Mon, Oct 21, 2024 at 11:35 AM Philipp Eppelt
>> >      >     <[email protected]
>> >     <mailto:[email protected]>
>> >     <mailto:[email protected] <mailto:
>> [email protected]>>
>> >      >      > <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>> wrote:
>> >      >      >
>> >      >      >     Hi Mohamed,
>> >      >      >
>> >      >      >     can you please check your arm64 build tree and look
>> into the
>> >     folder
>> >      >      >     'assets/dtb/'? There should be links to all the .dtb
>> files of
>> >     uvmm.
>> >      >     The link of
>> >      >      >     the file in question on my machine is:
>> >      >      >
>> >      >      >
>> >      >
>> >
>>  
>> [...]/.build-arm64/pkg/uvmm/configs/dts/OBJ-arm64_armv8a-std-l4f/virt-arm_virt-64_pci.dtb
>> >      >      >
>> >      >      >     If the file is missing in the linked folder, please
>> check the
>> >      >     corresponding
>> >      >      >     source directory:
>> >      >      >
>> >      >      >     <src>/pkg/uvmm/configs/dts/
>> >      >      >
>> >      >      >     If virt-arm_virt-64_pci.dts isn't in there, you can
>> download
>> >     it from our
>> >      >      >     development version of L4Re on github and recompile
>> the uvmm
>> >     package.
>> >      >      >
>> >      >      >
>> >      >
>> >
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts
>> <
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts>
>> <
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts
>> <
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts>>
>> <
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts
>> <
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts>
>> <
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts
>> <
>> https://github.com/kernkonzept/uvmm/blob/master/configs/dts/virt-arm_virt-64_pci.dts
>> >>>
>> >      >      >
>> >      >      >     If the file is there, please check that
>> '<arm64-build>/assets'
>> >      >     directory is in
>> >      >      >     your MODULE_SEARCH_PATH.
>> >      >      >
>> >      >      >     Let me know, if this solves the missing file problem.
>> >      >      >
>> >      >      >     Cheers,
>> >      >      >     Philipp
>> >      >      >
>> >      >      >
>> >      >      >
>> >      >      >     Am 20.10.24 um 09:20 schrieb Mohamed Dawod:
>> >      >      >      > Thanks Matthias
>> >      >      >      > I'm going to fix the typo of *virt-pci.dtbo*.
>> >      >      >      > What about the missing file
>> *dtb/virt-arm_virt-64_pci.dtb *?
>> >      >      >      >
>> >      >      >      >
>> >      >      >      > On Tue, Oct 15, 2024 at 11:58 PM Matthias Lange
>> >      >      >     <[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >     <mailto:[email protected] <mailto:
>> [email protected]>>>
>> >      >      >      > <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>>> wrote:
>> >      >      >      >
>> >      >      >      >     Hi Mohamed,
>> >      >      >      >
>> >      >      >      >     On [15-10-2024 16:59], Mohamed Dawod wrote:
>> >      >      >      >      > Hi,
>> >      >      >      >      > I was trying to run the L4 demo
>> *vm-basic-pci* for
>> >     *arm64*
>> >      >     using
>> >      >      >     the command
>> >      >      >      >      > $ make qemu E=vm-basic-pci
>> >      >      >      >      > but It didn't work because of the missing 2
>> files :
>> >      >      >      >      > * virt-arm_virt-64_pci.dtb : which is
>> requested by the
>> >      >      >     *modules.list* file
>> >      >      >      >      > in the line :
>> >      >      >      >      >
>> >      >      >      >      > > module[arch=arm64,fname=virt-pci.dtb]
>> >      >      >       dtb/virt-arm_virt-64_pci.dtb
>> >      >      >      >      >
>> >      >      >      >      > * virt-pci.dtbo : which is requested by the
>> >      >     *vm-basic-pci.cfg* by the
>> >      >      >      >      > configuration
>> >      >      >      >      >
>> >      >      >      >      > > if (L4.Info.arch() == "arm64") then
>> >      >      >      >      > >    dt = "-drom/.fdt"
>> >      >      >      >      > >    overlay = "*-drom/virt-pci.dtbo*"
>> >      >      >      >
>> >      >      >      >     This is actually a typo. Please change this
>> line to
>> >      >      >      >
>> >      >      >      >        overlay = "-drom/virt-pci.dtb"
>> >      >      >      >
>> >      >      >      >     Best,
>> >      >      >      >     Matthias.
>> >      >      >      >
>> >      >      >      >      > > else
>> >      >      >      >      > >    dt = "-drom/virt-pci.dtb"
>> >      >      >      >      > >    overlay = ""
>> >      >      >      >      > > end
>> >      >      >      >      >
>> >      >      >      >      >
>> >      >      >      >      > I searched for both files in the whole
>> >     *l4re-snapshot-23.10.1*
>> >      >      >     directory
>> >      >      >      >      > but I couldn't find them
>> >      >      >      >      > Where can I find those necessary files to
>> run
>> >      >     *vm-basic-pc*i demo?
>> >      >      >      >      >
>> >      >      >      >      > Thanks in advance,
>> >      >      >      >      > Regards
>> >      >      >      >      >
>> >      >      >      >      > --
>> >      >      >      >      > Mohamed Dawod
>> >      >      >      >      > *Software Engineer,* Cairo Egypt
>> >      >      >      >      >
>> >      >      >      >      > --
>> >      >      >      >      >
>> >      >      >      >      >
>> >      >      >      >      > *Driving Innovation! Visit our website
>> >     www.avelabs.com <http://www.avelabs.com>
>> >      >     <http://www.avelabs.com <http://www.avelabs.com>>
>> >      >      >     <http://www.avelabs.com <http://www.avelabs.com>
>> >     <http://www.avelabs.com <http://www.avelabs.com>>>
>> >      >      >      >     <http://www.avelabs.com <
>> http://www.avelabs.com>
>> >     <http://www.avelabs.com <http://www.avelabs.com>>
>> >      >     <http://www.avelabs.com <http://www.avelabs.com>
>> >     <http://www.avelabs.com <http://www.avelabs.com>>>>
>> >      >      >      >      > <http://www.avelabs.com/ <
>> http://www.avelabs.com/>
>> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>
>> >      >     <http://www.avelabs.com/ <http://www.avelabs.com/>
>> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>>
>> >      >      >     <http://www.avelabs.com/ <http://www.avelabs.com/>
>> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>
>> >      >     <http://www.avelabs.com/ <http://www.avelabs.com/>
>> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>>>>*, to read
>> Avelabs
>> >      >      >      >     Confidentiality Notice, follow
>> >      >      >      >      > this link:
>> >     http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>>
>> >      >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>>>
>> >      >      >      >      > <
>> http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>>
>> >      >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>>>>
>> >      >      >      >      >
>> >      >      >      >
>> >      >      >      >      >
>> _______________________________________________
>> >      >      >      >      > l4-hackers mailing list --
>> >     [email protected] <mailto:
>> [email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>
>> >      >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>>
>> >      >      >      >      > To unsubscribe send an email to
>> >      >      > [email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>
>> >      >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>>
>> >      >      >      >
>> >      >      >      >
>> >      >      >      >     --
>> >      >      >      >     Get started with L4Re in 3 days - register now
>> for our
>> >     workshop in
>> >      >      >     October!
>> >      >      >      >
>> >      >      >      >     Visit
>> >      > https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>
>> >      >     <
>> https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>>
>> >      >      >
>> >       <https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>
>> >      >     <
>> https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>>>
>> >      >      >      >
>> >      >       <
>> https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>
>> >      >     <
>> https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>>
>> >      >      >
>> >       <https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>
>> >      >     <
>> https://www.kernkonzept.com/workshop-getting-started-with-l4re
>> >     <https://www.kernkonzept.com/workshop-getting-started-with-l4re>>>>
>> to learn
>> >      >      >      >     more.
>> >      >      >      >
>> >      >      >      >     --
>> >      >      >      >     Matthias Lange                      phone: +49
>> (0)
>> >     351-41 888 614
>> >      >      >      >     Customer Engineer Specialist        web:
>> >      > https://www.kernkonzept.com <https://www.kernkonzept.com>
>> >     <https://www.kernkonzept.com <https://www.kernkonzept.com>>
>> >      >      >     <https://www.kernkonzept.com <
>> https://www.kernkonzept.com>
>> >     <https://www.kernkonzept.com <https://www.kernkonzept.com>>>
>> >      >      >      >     <https://www.kernkonzept.com
>> >     <https://www.kernkonzept.com> <https://www.kernkonzept.com
>> >     <https://www.kernkonzept.com>>
>> >      >     <https://www.kernkonzept.com <https://www.kernkonzept.com>
>> >     <https://www.kernkonzept.com <https://www.kernkonzept.com>>>>
>> >      >      >      >
>> >      >      >      >     Kernkonzept GmbH
>> >      >      >      >     Buchenstraße 16b
>> >      >      >      >     01097 Dresden
>> >      >      >      >
>> >      >      >      >     Geschäftsführer: Dr.-Ing. Michael Hohmuth
>> >      >      >      >     Registergericht: Amtsgericht Dresden
>> >      >      >      >     Handelsregister: HRB 31129
>> >      >      >      >
>> >      >      >      >     You might not be working when I am and that's
>> ok!
>> >     Please make
>> >      >     sure to
>> >      >      >     only
>> >      >      >      >     reply when it suits you. Mails can wait.
>> >      >      >      >
>> >      >      >      >
>> >      >      >      >
>> >      >      >      > *Driving Innovation! Visit our website
>> www.avelabs.com
>> >     <http://www.avelabs.com>
>> >      >     <http://www.avelabs.com <http://www.avelabs.com>>
>> >      >      >     <http://www.avelabs.com <http://www.avelabs.com>
>> >     <http://www.avelabs.com <http://www.avelabs.com>>>
>> >      >      >      > <http://www.avelabs.com/ <http://www.avelabs.com/>
>> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>
>> >      >     <http://www.avelabs.com/ <http://www.avelabs.com/>
>> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>>>*, to read
>> Avelabs
>> >      >      >     Confidentiality Notice, follow this
>> >      >      >      > link: http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>>
>> >      >      >      > <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >      >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>>>
>> >      >      >      >
>> >      >      >      > _______________________________________________
>> >      >      >      > l4-hackers mailing list --
>> [email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>
>> >      >      >      > To unsubscribe send an email to
>> >      > [email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>
>> >      >      >
>> >      >      >     --
>> >      >      > [email protected]
>> >     <mailto:[email protected]>
>> >     <mailto:[email protected] <mailto:
>> [email protected]>>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>> -
>> >      >      >     Tel. 0351-41 883 221
>> >      >      > http://www.kernkonzept.com <http://www.kernkonzept.com>
>> >     <http://www.kernkonzept.com <http://www.kernkonzept.com>>
>> >      >     <http://www.kernkonzept.com <http://www.kernkonzept.com>
>> >     <http://www.kernkonzept.com <http://www.kernkonzept.com>>>
>> >      >      >
>> >      >      >     Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht
>> Dresden, HRB 31129.
>> >      >      >     Geschäftsführer: Dr.-Ing. Michael Hohmuth
>> >      >      >     _______________________________________________
>> >      >      >     l4-hackers mailing list --
>> [email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>
>> >      >      >     To unsubscribe send an email to
>> >     [email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>
>> >      >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>
>> >      >     <mailto:[email protected]
>> >     <mailto:[email protected]>>>
>> >      >      >
>> >      >      >
>> >      >      >
>> >      >      > *Driving Innovation! Visit our website www.avelabs.com
>> >     <http://www.avelabs.com>
>> >      >     <http://www.avelabs.com <http://www.avelabs.com>>
>> >      >      > <http://www.avelabs.com/ <http://www.avelabs.com/>
>> >     <http://www.avelabs.com/ <http://www.avelabs.com/>>>*, to read
>> Avelabs
>> >      >     Confidentiality Notice, follow this
>> >      >      > link: http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >      >      > <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      >     <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>>
>> >      >
>> >      >     --
>> >      > [email protected] <mailto:
>> [email protected]>
>> >     <mailto:[email protected]
>> >     <mailto:[email protected]>> -
>> >      >     Tel. 0351-41 883 221
>> >      > http://www.kernkonzept.com <http://www.kernkonzept.com>
>> >     <http://www.kernkonzept.com <http://www.kernkonzept.com>>
>> >      >
>> >      >     Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB
>> 31129.
>> >      >     Geschäftsführer: Dr.-Ing. Michael Hohmuth
>> >      >
>> >      >
>> >      >
>> >      > *Driving Innovation! Visit our website www.avelabs.com
>> >     <http://www.avelabs.com>
>> >      > <http://www.avelabs.com/ <http://www.avelabs.com/>>*, to read
>> Avelabs
>> >     Confidentiality Notice, follow this
>> >      > link: http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>
>> >      > <http://www.avelabs.com/email/disclaimer.html
>> >     <http://www.avelabs.com/email/disclaimer.html>>
>> >
>> >     --
>> >     [email protected] <mailto:
>> [email protected]> -
>> >     Tel. 0351-41 883 221
>> >     http://www.kernkonzept.com <http://www.kernkonzept.com>
>> >
>> >     Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
>> >     Geschäftsführer: Dr.-Ing. Michael Hohmuth
>> >
>> >
>> >
>> > *Driving Innovation! Visit our website www.avelabs.com
>> > <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice,
>> follow this
>> > link: http://www.avelabs.com/email/disclaimer.html
>> > <http://www.avelabs.com/email/disclaimer.html>
>>
>> --
>> [email protected] - Tel. 0351-41 883 221
>> http://www.kernkonzept.com
>>
>> Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
>> Geschäftsführer: Dr.-Ing. Michael Hohmuth
>>
>

-- 


*Driving Innovation! Visit our website www.avelabs.com 
<http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow 
this link: http://www.avelabs.com/email/disclaimer.html 
<http://www.avelabs.com/email/disclaimer.html>

_______________________________________________
l4-hackers mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to