From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 9front and raspberry pi 4 8gb model
Date: Wed, 3 Jun 2020 07:34:46 +0000 [thread overview]
Message-ID: <CAFSF3XOYNJy6c-n9cgcDSQ-YcZ4oHO3a2JdWg9cwM+f6jCg7UA@mail.gmail.com> (raw)
In-Reply-To: <CAHwi9bztTK0W31TAnVhRs6cUpn89zUSHnM0yt-pkpcPX2YCYpA@mail.gmail.com>
yes, the rpi people left away some flash and now the software has to
provide a certain additional firmware. somebody (i didn't recognize
his name) fixed it already according to the rpi github pages, but i
don't know if they provided any patches for the rest of us :(
cinap doesn't have an 8gb model, so it would be a waste of time for
him to remote-guess all these little undocumented changes the rpi
foundation is making.
On 6/2/20, Eli Cohen <echoline@gmail.com> wrote:
> I was lurking in the channel and saw cinap complaining a later rpi
> requires a firmware upload for the xhci to work. He may have meant
> your model rpi4. We have to be patient or code it ourselves not as
> well as he would, he is only one man
>
> On Tue, Jun 2, 2020 at 4:12 PM JimErickson <jimerickso@gmail.com> wrote:
>>
>> i have a raspberry pi 4 4gb model and a raspberry pi 4 8gb model. 9front
>> runs just fine on the 4gb model but on the 8gb model the keyboard and
>> mouse are not detected. both models have the same firmware and eeprom,
>> the latest release dated april 23, 2020. am i doing something wrong or
>> has something changed on the usb bus on the 8gb model?
>>
>
>
> --
> http://echoline.org
>
next prev parent reply other threads:[~2020-06-03 7:34 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 [this message]
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
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=CAFSF3XOYNJy6c-n9cgcDSQ-YcZ4oHO3a2JdWg9cwM+f6jCg7UA@mail.gmail.com \
--to=23hiro@gmail.com \
--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).