From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] 9front and raspberry pi 4 8gb model
Date: Thu, 4 Jun 2020 19:21:44 +0200 [thread overview]
Message-ID: <8E4C3147C1267DCDC62534C942FF1A46@felloff.net> (raw)
In-Reply-To: <5cf90fb3-af57-15ce-ff44-68cf884a7d2a@gmail.com>
i do know as much as you about this issue.
maybe you also need to update bootcode.bin in the image?
or it needs another device tree file? or some new file we dont
know about?
the next steps would be to print the return value of xhcireset()...
maybe that can give us a hint if the command was supported by the
firmware or not.
you can also ask richard miller about this... maybe download his
image and see if this works. and see what firmware and device tree
files he has there.
we could also to take a look at raspbian image. and in see what
they do in the linux kernel.
the diff i send is based on richard millers patch.
i only tested that it doesnt break my raspberry pi 4 with 1gb ram.
i had to move the xhcireset() call to archinit() tho which is
basically just after pci controller reset and after we mapped
the bus and programmed the membars.
originally, the xhcireset() call was after firmware handoff in
the usbxhci driver itself, but i asked richard if he could try
to do the reset earlier because our xhci driver is in port/,
and this is very raspberry pi specific quirk that doesnt belong
into the portable driver.
richard confirmed that it still works when doing the firmware
call before the pcienable(), but maybe theres some other side
effect. could even be just timing.
good luck.
--
cinap
next prev parent reply other threads:[~2020-06-04 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 23:12 JimErickson
2020-06-02 23:23 ` [9front] " Eli Cohen
2020-06-03 7:34 ` hiro
2020-06-03 13:05 ` JimErickson
2020-06-03 17:58 ` cinap_lenrek
2020-06-03 18:28 ` hiro
2020-06-04 1:46 ` JimErickson
2020-06-04 1:57 ` ori
2020-06-04 15:30 ` JimErickson
2020-06-04 17:21 ` cinap_lenrek [this message]
2020-06-05 0:14 ` JimErickson
2020-07-02 19:27 ` cinap_lenrek
2020-07-02 22:27 ` Roman Shaposhnik
2020-06-11 17:46 ` cinap_lenrek
2020-06-13 18:58 ` Roman Shaposhnik
2020-06-14 1:56 ` cinap_lenrek
2020-06-14 2:43 ` Roman Shaposhnik
2020-06-04 17:37 ` cinap_lenrek
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=8E4C3147C1267DCDC62534C942FF1A46@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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).