Hi
> I would like to try to connect some serial hardware simulation to a standard
> serial port within qemu. Everything should run within qemu.
I found the answer and just to make the people happy using search engines
here is the answer:
There are backends which already implement serial hardware
Hi
I would like to try to connect some serial hardware simulation to a standard
serial port within qemu. Everything should run within qemu.
The closest i found was qemu_chr_open_pipe but then there seem to be no uses
within the qemu code which made me suspicious. It also made it hard finding
so
available named i2c-tiny-usb.
+ *
+ * Below is an example how to use this device from command line:
+ * -device usb-i2c-tiny,id=i2c-0 -device tmp105,bus=i2c,address=0x50
+ *
+ * Copyright (c) 2015 Tim Sander
+ *
+ * Loosly based on usb dev-serial.c:
+ * Copyright (c) 2006 CodeSourcery
/index.shtml
It is pretty simple and has no usb endpoints just a control.
Reasons for adding this device:
* Linux device driver available
* adding an additional i2c bus via command line e.g.
-device usb-i2c-tiny,id=i2c-0 -device tmp105,bus=i2c,address=0x50
---
Signed-off-by: Tim Sander
default
usb endpoints just a control.
Reasons for adding this device:
* Linux device driver available
* adding an additional i2c bus via command line e.g.
-device usb-i2c-tiny,id=i2c-0 -device tmp105,bus=i2c,address=0x50
---
Signed-off-by: Tim Sander
default-configs/usb.mak | 1 +
hw/usb/Makefile.objs
,id=i2c-0 -device tmp105,bus=i2c,address=0x50
---
Signed-off-by: Tim Sander
default-configs/usb.mak | 1 +
hw/usb/Makefile.objs| 1 +
hw/usb/dev-i2c-tiny.c | 314
trace-events| 11 ++
4 files changed, 327 insertions(+)
create
Hi
Am Donnerstag, 7. Januar 2016, 02:14:23 schrieb Peter Crosthwaite:
> Patch subject prefix should contain the version number. Use the
> --subject-prefix or -v options to git format-patch.
Ok, i will try to remember this next time.
>
> On Wed, Jan 6, 2016 at 6:58 AM, Tim S
Version 4 with improvements suggested by Gerd Hoffmann:
Signed-off-by: Tim Sander
i2c-tiny-usb is a small usb to i2c bridge:
http://www.harbaum.org/till/i2c_tiny_usb/index.shtml
It is pretty simple and has no usb endpoints just a control.
Reasons for adding this device:
* Linux device driver
Hi Gerd
Thanks for your review.
Am Dienstag, 5. Januar 2016, 08:44:30 schrieb Gerd Hoffmann:
> > +case 0x4107:
> > +/* this seems to be a byte type access */
> > +if (i2c_start_transfer(s->i2cbus, /*address*/index, 0)) {
> > +trace_usb_i2c_tiny_i2c_start_transfer_f
Version 3 with improvements suggested by Gerd Hoffmann
Signed-off-by: Tim Sander
i2c-tiny-usb is a small usb to i2c bridge
Hi
Below is a patch from Jan Kiszka
https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg05714.html
but in one part and adapted to block layer changes. I would like to get
this work mainlined and my question is whats missing to get this stuff
mainlined?
As far as i understand Jan is ok with
Signed-off-by: Tim Sander
i2c-tiny-usb is a small usb to i2c bridge:
http://www.harbaum.org/till/i2c_tiny_usb/index.shtml
It is pretty simple and has no usb endpoints just a control.
Reasons for adding this device:
* Linux device driver available
* adding an additional i2c bus via command line
Hi Jan
Am Donnerstag, 10. Dezember 2015, 13:57:47 schrieb Jan Kiszka:
> > I have seen your patches for AT24Cxx functionality in qemu:
> > https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg05714.html
> >
> > As i am interested in this work i am wondering what happend to this
> > effort?
>
Hi Jan
I have seen your patches for AT24Cxx functionality in qemu:
https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg05714.html
As i am interested in this work i am wondering what happend to this effort?
Best regards
Tim
Hi Paolo and List
Am Freitag, 27. November 2015, 13:53:22 schrieb Paolo Bonzini:
> On 27/11/2015 13:39, Tim Sander wrote:
> > I have one more thing, i2cdetect looks like this:
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> >
> > 00: 03 04 05 06
Hi
We are trying to call "inject_nmi" from a device on a x386 target.
Unfortunatly it gets called with the wrong defines and the define
TARGET_I386 is *not* defined. If we define TARGET_I386 for testing
the code in the defines fails to compile.
Trying to fix this by including:
"qom/cpu.h" and "
Hi Paolo
Am Freitag, 27. November 2015, 10:32:25 schrieb Paolo Bonzini:
> On 26/11/2015 17:35, Tim Sander wrote:
> > Below is a patch implementing the i2c-tiny-usb device.
> > I am currently not sure about the i2c semantics. I think
> > incrementing the address on longer rea
Am Freitag, 27. November 2015, 07:48:21 schrieb Gerd Hoffmann:
> On Do, 2015-11-26 at 17:35 +0100, Tim Sander wrote:
> > Hi
> >
> > Below is a patch implementing the i2c-tiny-usb device.
>
> Is there a specification for this kind of device?
http://www.harbaum.org/ti
Hi Alex
Thanks for your feedback, answers as usual inline.
Am Donnerstag, 26. November 2015, 18:07:35 schrieb Alex Bennée:
> Tim Sander writes:
> > Hi
> >
> > Below is a patch implementing the i2c-tiny-usb device.
> > I am currently not sure about the i2c semantic
-smartcard-reader.o
diff --git a/hw/usb/dev-i2c-tiny.c b/hw/usb/dev-i2c-tiny.c
new file mode 100644
index 000..1dabb36
--- /dev/null
+++ b/hw/usb/dev-i2c-tiny.c
@@ -0,0 +1,383 @@
+/*
+ * I2C tiny usb device emulation
+ *
+ * Copyright (c) 2015 Tim Sander
+ *
+ * Loosly based on usb dev-serial.c:
+ *
Hi
I am no so far that i can successfully read and write from linux usermode to
my virtual i2c-tiny-usb device. Unfortunatly i was not able to plug any i2c-
device into this device to go on with implementing the backend bus accesses.
I can instantiate my i2c-tiny-usb with the following command l
Hi Paolo
Am Dienstag, 17. November 2015, 15:12:29 schrieb Paolo Bonzini:
> On 17/11/2015 14:45, Tim Sander wrote:
> > I just gave it a try and now i have a device which is detected by linux
> > and
> > allows simple reads (without i2c backend though). But unfortunatly i am
&
Hi Paolo
Thanks for your reply.
Am Dienstag, 17. November 2015, 15:12:29 schrieb Paolo Bonzini:
> On 17/11/2015 14:45, Tim Sander wrote:
> > I just gave it a try and now i have a device which is detected by linux
> > and
> > allows simple reads (without i2c backend though).
ut is just
controlled via the usb control. The device fragment is attached.
Thanks
Tim
/*
* I2C tiny usb device emulation
*
* Copyright (c) 2015 Tim Sander
*
* Loosly based on usb dev-serial.c:
* Copyright (c) 2006 CodeSourcery.
* Copyright (c) 2008 Samuel Thibault
* Written by Paul
Hi Greg
Am Freitag, 14. November 2014, 10:50:40 schrieb Greg Bellows:
> On 14 November 2014 09:34, Tim Sander wrote:
> > > > > 0xbfffe000? You where talking about the fact that the security
> > > > > extensions
> > > > > where not implem
> > > 0xbfffe000? You where talking about the fact that the security
> > > extensions
> > > where not implemented. I was not aware that the different vbar's where
> > > already part of the security stuff?
> >
> > MVBAR is part of the Security extensions. HVBAR is part of the
> > Virtualization ext
Am Donnerstag, 13. November 2014, 09:09:33 schrieb Greg Bellows:
> On 13 November 2014 07:58, Tim Sander wrote:
> > Am Mittwoch, 12. November 2014, 10:00:03 schrieb Greg Bellows:
> > > On 12 November 2014 07:56, Tim Sander wrote:
> > > > Hi Greg
> > >
Am Mittwoch, 12. November 2014, 10:00:03 schrieb Greg Bellows:
> On 12 November 2014 07:56, Tim Sander wrote:
> > Hi Greg
> >
> > > > Bad mode in data abort handler detected
> > > > Internal error: Oops - bad mode: 0 [#1] PREEMPT SMP ARM
> > > >
Hi Greg
> > Bad mode in data abort handler detected
> > Internal error: Oops - bad mode: 0 [#1] PREEMPT SMP ARM
> > Modules linked in: firq(O) ipv6
> > CPU: 0 PID: 103 Comm: systemd-udevd Tainted: G O 3.14.0 #1
> > task: bf2b9300 ti: bf362000 task.ti: bf362000
> > PC is at 0x1240
> >
Hi Greg
> Ah... Yes, using A9 (GICv1) which means you don't have grouping without the
> security extensions.
Ok switching the GIC to version 2 works seems to work. In a way that Linux still
boots up and i get a FIQ.
I have some problems still:
It seems as if the exeption of the bugsplat below
is
Hi Greg
Thanks for your fast reply.
> I am still in the process of getting the security extension portion of the
> GIC patches fully up and running. By the sounds of your use, it sounds
> like you just want FIQ support not necessarily secure GIC support. Would
> this be correct?
Yes. More elabor
Hi
I am currently wetting my toes with qemu. I have written a small test hw
device which creates interrupts and has some registers on a arm vexpress
platform. Now i would like to switch the interrupt of the hw to FIQ mode.
I noticed that the mainline qemu does not seem to have FIQ emulation but
32 matches
Mail list logo
