From: Benoit Canet <benoit.canet@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Fix] Musicpal I2C bitbanging extraction and Versatile I2C device creation
Date: Fri, 14 Aug 2009 22:23:11 +0200 [thread overview]
Message-ID: <1250281397-7660-1-git-send-email-benoit.canet@gmail.com> (raw)
In-Reply-To: <n>
Hello,
This is a rework of the patches extracting the I2C bitbanging code
from musicpal.c
-A bug added in the previous version which was breaking reads from I2C
slaves
is now fixed.
-Two new patches add I2C support the versatilepb board.
The I2C module now work fine with the musicpal firmware and with a
24c02 eeprom connected to the versatile board.
The I2C bitbanging code may be rewrited later following
the ideas Paul Brook emitted on IRC a few time ago.
I'm new to QEMU and motivated to contribute back the changes we've made
so any hints on how to get theses patches in a mergeable state are
welcome.
Regards
Benoit
next reply other threads:[~2009-08-14 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 20:23 Benoit Canet [this message]
2009-08-14 20:23 ` [Qemu-devel] [PATCH 1/9] Musicpal qdev conversion : gpio (except I2C part), keyboard and lcd Benoit Canet
2009-08-14 20:23 ` [Qemu-devel] [PATCH 2/9] Extract musicpal.c I2C bitbanging code and make it gpio aware Benoit Canet
2009-08-14 20:23 ` [Qemu-devel] [PATCH 3/9] Extract the Marvell 88w8618 audio device from musicpal.c Benoit Canet
2009-08-14 20:23 ` [Qemu-devel] [PATCH 4/9] Make musicpal.c use the I2C device and the Marvell 88w8618 audio device Benoit Canet
2009-08-14 20:23 ` [Qemu-devel] [PATCH 5/9] Create a Versatile I2C device using the I2C bitbanging module Benoit Canet
2009-08-14 20:23 ` [Qemu-devel] [PATCH 6/9] Add the Versatile I2C device to versatilepb.c Benoit Canet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1250281397-7660-1-git-send-email-benoit.canet@gmail.com \
--to=benoit.canet@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).