From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>
Subject: [PATCH v2 0/3] e1000: fix access to companion flash chip
Date: Mon, 9 Oct 2017 21:06:24 +0200 [thread overview]
Message-ID: <20171009190627.2486-1-u.kleine-koenig@pengutronix.de> (raw)
Hello,
this is v2 of the series. Compared to (implicit) v1 I worked in Andrey's
feedback and updated the commit logs. The third patch is not marked as
HACK any more (and got some reformatting). In the mean time I also
tested successfully the write support. For NDA reasons I don't have
access to firmware, so making full use of a i210 after flashing is not
tested yet.
Even though I changed a few bits in the first two patches, I already
added the acks by Andrey that I got for v1.
Best regards
Uwe
Uwe Kleine-König (3):
e1000: implement register mapping for E1000_FLSW{CTL,DATA,CNT}
e1000: implement support for smaller flash chips
e1000: Don't poll for FLSWCTL.GLDONE before starting a flash
transaction
drivers/net/e1000/e1000.h | 9 +++------
drivers/net/e1000/eeprom.c | 27 +++++----------------------
drivers/net/e1000/regio.c | 9 +++++++++
3 files changed, 17 insertions(+), 28 deletions(-)
--
2.11.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-10-09 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 19:06 Uwe Kleine-König [this message]
2017-10-09 19:06 ` [PATCH v2 1/3] e1000: implement register mapping for E1000_FLSW{CTL, DATA, CNT} Uwe Kleine-König
2017-10-09 19:06 ` [PATCH v2 2/3] e1000: implement support for smaller flash chips Uwe Kleine-König
2017-10-09 19:06 ` [PATCH v2 3/3] e1000: Don't poll for FLSWCTL.GLDONE before starting a flash transaction Uwe Kleine-König
2017-10-16 8:26 ` [PATCH v2 0/3] e1000: fix access to companion flash chip Sascha Hauer
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=20171009190627.2486-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.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