From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Raspberry Pi 4
Date: Thu, 25 Jul 2019 09:37:11 +0200 [thread overview]
Message-ID: <5BBA1B01D4D0B72B1383A538D9CBE6CC@felloff.net> (raw)
In-Reply-To: 37ae6947ce6aa50686758231a29657f0@hamnavoe.com
i just commited everything i got for the raspberry pi 4.
sorry that this took so long. i was trying to get
the ethernet reliable but this has some bizzare issue
that i was unable to resolve.
http://code.9front.org/hg/plan9front/rev/889b634159e5
http://code.9front.org/hg/plan9front/rev/55d93e47a2de
http://code.9front.org/hg/plan9front/rev/686cdda01118
http://code.9front.org/hg/plan9front/rev/4dbf2522f668
http://code.9front.org/hg/plan9front/rev/db3e8d004b27
http://code.9front.org/hg/plan9front/rev/5afd2605d0f3
http://code.9front.org/hg/plan9front/rev/6e8b95bccec4
http://code.9front.org/hg/plan9front/rev/234f51ace8cd
http://code.9front.org/hg/plan9front/rev/406bef7018a8
http://code.9front.org/hg/plan9front/rev/386fe43162b4
http://code.9front.org/hg/plan9front/rev/f3966b67adc9
note, this is a arm64 kernel, but the drivers should be portable.
- interrupts, uart, multicore, graphics and /dev/reboot works
- pcie and xhci works
- genet works somewhat (good enougth for /dev/reboot netbooting) but
causes bizzare 42 second bus stalls with bursty bidirectional
ethernet traffic which hangs all gisb devices (pcie/xhci)
i'll write you the details and what i tried about that ethernet
issue offlist, maybe we can figure this out together.
--
cinap
next reply other threads:[~2019-07-25 7:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 7:37 cinap_lenrek [this message]
2019-07-25 9:15 ` Richard Miller
-- strict thread matches above, loose matches on Subject: below --
2019-09-25 20:58 Richard Miller
2019-09-29 20:32 ` David du Colombier
2019-08-25 11:09 Richard Miller
2019-07-25 11:41 cinap_lenrek
2019-07-25 11:19 cinap_lenrek
2019-07-25 9:35 cinap_lenrek
2019-07-25 10:02 ` Richard Miller
2019-07-25 10:04 ` Richard Miller
2019-07-18 13:32 Richard Miller
2019-07-19 9:19 ` hiro
2019-07-19 9:41 ` Richard Miller
2019-07-19 9:45 ` hiro
2019-07-19 9:49 ` Richard Miller
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=5BBA1B01D4D0B72B1383A538D9CBE6CC@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).