From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Raspberry Pi 4
Date: Thu, 25 Jul 2019 11:35:39 +0200 [thread overview]
Message-ID: <CBA57E1486BAEF74750CB5A25D52D441@felloff.net> (raw)
In-Reply-To: cd636a3c97ed194b29aea601e9bdce8f@hamnavoe.com
> Thanks, I'll take a look at this. Have you seen any pi4 h/w docs
> or have you been working just from linux drivers?
no, i wish. only reading linux source and deciphering device tree
mazes. :(
> I've been stalled on getting ether4330 to initialise. Putting
> some coherence() calls into emmc.c helped (I don't like
> out-of-order cpus) but I keep getting spurious interrupt 1023
> followed by watchdog reboot.
i dont know anything about the 4330.
i think theres a bug with the dma code tho. you actually need to
invalidate caches *AFTER* the hw completed because the
core can speculatively prefetch memory and bring it into the
cache before the hardware is done writing memory. iirc the
code just cleans/invalidates BEFORE issuing the dma operation.
> Do you have the sdcard working? According to a pi engineer,
> the new emmc controller is sdhci compliant so it shouldn't
> be hard.
i have not tried sdcard yet.
--
cinap
next reply other threads:[~2019-07-25 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:35 cinap_lenrek [this message]
2019-07-25 10:02 ` Richard Miller
2019-07-25 10:04 ` 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 7:37 cinap_lenrek
2019-07-25 9:15 ` 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=CBA57E1486BAEF74750CB5A25D52D441@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).