From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4)
Date: Wed, 3 Aug 2022 13:41:48 +0100 [thread overview]
Message-ID: <41610f28d984a2c746112264c283d539@hamnavoe.com> (raw)
In-Reply-To: <62cdf382-8f79-b163-d63a-5991b0f96be1@SDF.ORG>
> By the way Richard, should I take the last rpi image at 9legacy as
> the more recent with your work? Are you going to abandon
> https://plan9.io/sources/contrib/miller/?
9legacy should always have up to date patches for the Raspberry Pi, and
the 9legacy SD card image will usually be fresher than the 9pi.img.gz
image in contrib/miller. The only value now in the 9pi image is for
historians: I've tried to conserve the metadata so it's possible to see
when source files were most recently changed. On 9legacy, patches are
re-applied when a distribution image is made, so mtime information is
less informative.
I will also continue to maintain the Pi kernel source in contrib/miller/9/bcm,
where a more complete history can be seen:
term% srv -n 9p.io sources
post...
term% history /n/sources/contrib/miller/9/bcm/etherusb.c
Aug 3 13:16:49 BST 2022 /n/sources/contrib/miller/9/bcm/etherusb.c 8872 [miller]
Jul 18 13:26:35 BST 2019 /n/sourcesdump/2022/0803/contrib/miller/9/bcm/etherusb.c 8888 [miller]
Apr 4 17:04:17 BST 2018 /n/sourcesdump/2019/0718/contrib/miller/9/bcm/etherusb.c 8837 [bootes]
Mar 4 21:18:17 GMT 2016 /n/sourcesdump/2018/0404/contrib/miller/9/bcm/etherusb.c 7878 [bootes]
Jul 2 09:00:28 BST 2015 /n/sourcesdump/2016/0304/contrib/miller/9/bcm/etherusb.c 7838 [bootes]
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T668643d11149fab4-M67bb6396df945caf4d9c54df
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-08-03 12:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 17:58 adr
2022-07-31 18:08 ` hiro
2022-07-31 18:09 ` adr
2022-07-31 21:35 ` Richard Miller
2022-08-01 9:16 ` Richard Miller
2022-08-01 16:29 ` adr
2022-08-02 8:50 ` Richard Miller
2022-08-03 0:34 ` adr
2022-08-03 3:00 ` adr
2022-08-03 10:57 ` Richard Miller
2022-08-03 18:46 ` adr
2022-08-04 10:13 ` Richard Miller
2022-08-04 11:56 ` ori
2022-08-04 19:34 ` adr
2022-08-05 12:14 ` ori
2022-08-01 16:43 ` adr
2022-08-01 17:06 ` adr
2022-08-02 3:45 ` Lucio De Re
2022-08-02 9:07 ` Richard Miller
2022-08-03 0:52 ` adr
2022-08-03 1:08 ` adr
2022-08-03 12:41 ` Richard Miller [this message]
2022-08-03 18:47 ` adr
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=41610f28d984a2c746112264c283d539@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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).