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: Sat, 13 Jun 2015 21:06:05 +0900 [thread overview]
Message-ID: <20150613120604.GA3521@katana> (raw)
In-Reply-To: <CAMQCnXGQTQdXaOL5vT0ZbV-F_0P5qJ7kSQSHrMv49fMbAy2UrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
> Sorry to hackle you more but I am still getting the continuous message
> (when the console log level has changed to 8):
>
> i2c-slave-eerpom 1-0028: uevent
I will check that next week when I am back. I didn't use udev or
something similar when developing this framework, so I didn't notice.
> Should I just ignore this for now and see if I can get the slave
> support to work or do you think this might be in an issue in my
> implementation of the slave support in the xilinx driver.
Since I don't know and can't test anything at the moment, I'd say just
keep going :)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-06-13 12:06 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 ` I2C slave support on Xilinx Zybo Wolfram Sang
[not found] ` <CAMQCnXHfcgWpAS4HT=8sCt7RHA29xMK9KzAU6H0rP3RR7DLMuw@mail.gmail.com>
[not found] ` <CAMQCnXHfcgWpAS4HT=8sCt7RHA29xMK9KzAU6H0rP3RR7DLMuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-13 9:49 ` 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 [this message]
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=20150613120604.GA3521@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).