I haven't had any trouble with wifi on the 4, with one caveat. The 400 (and
maybe some of the later 4s) have an updated version of the radio. It just
takes a new entry in ether4330.c and new blobs in /sys/lib/firmware. The entry
I've got in my ether4330.c is:
{ 0x4345, 9,
My two cents on this:
What you _would_ want for this would be the ability to walk from the existing
fd, however the limits of 9p walk make this a bit impossible to implement in a
great way in my opinion. From walk(5):
The fid must represent a directory unless zero path name elements(for just
That's great, now I just need to get wifi to work... I can't get a definitive
answer on RPi 4 wifi is even supported.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M0bb93f82eedab10f21146c19
Delivery options:
On Fri, Apr 5, 2024, 23:49 Alyssa M via 9fans <9fans@9fans.net> wrote:
> Are you thinking narrowly about "What changes to the Plan 9 kernel would
> you make to emulate the Linux openat() system call" or more generally about
> "How would you design a facility for plan 9 that provides an equivalent
Are you thinking narrowly about "What changes to the Plan 9 kernel would you
make to emulate the Linux openat() system call" or more generally about "How
would you design a facility for plan 9 that provides an equivalent service?
As I understand it from the rationale section on the linux man
To me this sounds very similar to open() given a path relative to your current
working directory.
> On Apr 5, 2024, at 2:22 PM, ron minnich wrote:
>
> not so much what I want, I'm curious about ideas people have about
> implementing it that I would not think of.
>
> On Fri, Apr 5, 2024 at
not so much what I want, I'm curious about ideas people have about
implementing it that I would not think of.
On Fri, Apr 5, 2024 at 1:38 PM Gorka Guardiola wrote:
> Hmm sorry. Now I see what you want. Not to rewalk. You can use the chan of
> the dirfd and walk just the remainder cloning it and
Hmm sorry. Now I see what you want. Not to rewalk. You can use the chan of
the dirfd and walk just the remainder cloning it and creating a new one.
That way the openat provides the guarantees you want.
On Fri, Apr 5, 2024, 22:15 Gorka Guardiola wrote:
> I mean, if you want a new syscall jus
I mean, if you want a new syscall jus copy or call the implementation of
these.
On Fri, Apr 5, 2024, 22:12 Gorka Guardiola wrote:
> ¿Isn't that fd2path, strcat and open?
> Or am I misunderstanding something?
>
> On Fri, Apr 5, 2024, 21:51 ron minnich wrote:
>
>> One of the folks I worked
¿Isn't that fd2path, strcat and open?
Or am I misunderstanding something?
On Fri, Apr 5, 2024, 21:51 ron minnich wrote:
> One of the folks I worked with, when we pulled a big chunk of plan 9 into
> akaros, commented that he had implemented openat on akaros.
>
> I don't want this to turn into a
One of the folks I worked with, when we pulled a big chunk of plan 9 into
akaros, commented that he had implemented openat on akaros.
I don't want this to turn into a debate on the merits of openat; I am more
curious: if you went to implement openat on Plan 9, how would you go about
it? I have a
I was able to remove the black border by appending the following lines to
config.txt:
hdmi_group=2
hdmi_mode=82
hdmi_cvt=1920 1080 60 3 0 0 1
framebuffer_width=1920
framebuffer_height=1080
max_framebuffer_width=1920
max_framebuffer_height=1080
The lesson I learned was that the Pi needs to be
Oooh! More pixels!
This is wonderful, thank you!
I had the same situation, but I didn't know this was possible.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M02cd60501c363e99ed9163bd
Delivery options:
Dear 9fans,
I am booting my Raspberry Pi 4B off the 9legacy SD card image
(http://www.9legacy.org/download.html) and it boots fine with the default
config.txt, but there is a 48-pixel wide black border on the screen.
term% echo `{ dd -if /dev/screen -bs 64 -count 1}
0+1 records in
0+1
14 matches
Mail list logo
