From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Tim Bakker <bakkert-Lqq7FYbpbC48+Wv5JVE8qw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: I2C slave support on Xilinx Zybo
Date: Wed, 10 Jun 2015 23:38:02 +0900 [thread overview]
Message-ID: <20150610143801.GB21540@katana> (raw)
In-Reply-To: <CAMQCnXF47Kr3x3yeqba-me+N8rQ-vDJ6ziho5107qcckDbT0mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
Hi,
> I am currently working on getting slave support for the Xilinx Zybo platform
> with kernel version 3.19.0.
Cool! Any code you can show for the xilinx driver?
> These are the steps I have taken so far in userspace:
>
> # echo eeprom 0x28 > /sys/bus/i2c/devices/i2c-1/new_device
> # i2c i2c-1: new_device: Instantiated device eeprom at 0x29
Ehrm, no, you need to use the slave eeprom driver here. Gosh, did I
paste the wrong shell command into the docs? How emberrasing...
> I am new to asking question within the kernel emailing list, so I hope I do not
> offend anybody and I am certainly not trying.
No worries, you came to the right place.
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-06-10 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMQCnXF47Kr3x3yeqba-me+N8rQ-vDJ6ziho5107qcckDbT0mQ@mail.gmail.com>
[not found] ` <CAMQCnXF47Kr3x3yeqba-me+N8rQ-vDJ6ziho5107qcckDbT0mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-10 14:38 ` Wolfram Sang [this message]
[not found] ` <CAMQCnXHfcgWpAS4HT=8sCt7RHA29xMK9KzAU6H0rP3RR7DLMuw@mail.gmail.com>
[not found] ` <CAMQCnXHfcgWpAS4HT=8sCt7RHA29xMK9KzAU6H0rP3RR7DLMuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-13 9:49 ` I2C slave support on Xilinx Zybo Wolfram Sang
2015-06-13 10:17 ` Tim Bakker
[not found] ` <CAMQCnXGQTQdXaOL5vT0ZbV-F_0P5qJ7kSQSHrMv49fMbAy2UrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-13 12:06 ` Wolfram Sang
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=20150610143801.GB21540@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=bakkert-Lqq7FYbpbC48+Wv5JVE8qw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).