Is there a way to look for text in tags?
My instinct was to type in the topmost tag, then perform a button-3
click. It did not work.
A round-about way is to execute
<9p read acme/index
and look for it there (using plan9port, much appreciated if I can be
directed to the right place to ask if th
Hi,
On 08/21, Yuning Feng wrote:
> Is there a way to look for text in tags?
>
> My instinct was to type in the topmost tag, then perform a button-3
> click. It did not work.
>
> A round-about way is to execute
>
> <9p read acme/index
Not bad, just put wrap it in a script maybe ? I wonder if the p
from inside acme win (rc) session:
% grep channel.c /mnt/acme/[1-9]*/tag
/mnt/acme/70/tag:/sys/src/libthread/channel.c Del Snarf | Look
On Wed, Aug 21, 2019 at 6:12 AM Yuning Feng
wrote:
> Is there a way to look for text in tags?
>
> My instinct was to type in the topmost tag, then perform a
i'v made a sdcard image for the new raspberry pi 4
(also works on 3).
http://gabe.felloff.net/usr/cinap_lenrek/9front-7336.bb28fe19fe44.pi3.img.gz
this has support for most of the new hardware:
sdcard, ethernet and usb3.0
can someone please test this on the 2GB and 4GB
ram variants for me?
--
On Wed, 21 Aug 2019 19:56:08 +0200 cinap_len...@felloff.net wrote:
> i'v made a sdcard image for the new raspberry pi 4
> (also works on 3).
>
> http://gabe.felloff.net/usr/cinap_lenrek/9front-7336.bb28fe19fe44.pi3.img.gz
>
> this has support for most of the new hardware:
>
> sdcard, ethernet and u
> 512M memory: 207M kernel data, 304M user, 1828M swap
The firmware on a pi4 with 2GB or 4GB RAM will only report 1GB.
I believe you need to look at the board id (or probe for invalid
addresses as in the teg2 kernel) to find out the real amount.
thank you!
i believe its just starting rio so you dont get any more output.
interestingly, the framebuffer was set up without error as
far as the kernel is concerned. otherwise we would get an
error when trying to attach devdraw.
on the bootargs prompt, enter:
!rc
then on the rc shell:
cat '#
Back in the arm32 world, the contrib/miller/9/bcm kernel source
is now stable and useable on pi4, after fixing some old emmc bugs,
and thanks to cinap for spotting that no-execute bits have to be
set in device space page tables to prevent speculative instruction
fetches from device registers (!).
> cat '#ec/*maxmem'
% cat '#ec/*maxmem'
cat: can't open #ec/*maxmem: '#ec/*maxmem' file does not exist
% ls '#ec'
'#ec/8250.nr_uarts'
'#ec/bcm2708_fb.fbdepth'
'#ec/bcm2708_fb.fbheight'
'#ec/bcm2708_fb.fbswap'
'#ec/bcm2708_fb.fbwidth'
'#ec/cma'
'#ec/coherent_pool'
'#ec/console'
'#ec/smsc95xx.macadd
> ba...@bitblocks.com>:
> Trying this on pi4B4GB
>
> - no display
The display does come up for me (using HDMI0 socket).
On Wed, 21 Aug 2019 21:05:20 +0100 Richard Miller <9f...@hamnavoe.com> wrote:
> > ba...@bitblocks.com>:
> > Trying this on pi4B4GB
> >
> > - no display
>
> The display does come up for me (using HDMI0 socket).
It is an early 4k Seiki TV/Monitor. It works fine on a pi3
(running your kernel) in 14
ok, i prepared a kernel with debug prints. (i basically
buffer the debug outputs in kmesg and dump them on the
serial console and screen once they get initialized).
http://felloff.net/usr/cinap_lenrek/9pi4
i suspect that the device tree /memory/reg property
might not be a single 12 byte entry. an
> The firmware on a pi4 with 2GB or 4GB RAM will only report 1GB.
> I believe you need to look at the board id (or probe for invalid
> addresses as in the teg2 kernel) to find out the real amount.
oh dear. i dont even know the expected physical memory map...
i guess that ram is continuous block at
On Wed, 21 Aug 2019 23:59:28 +0200 cinap_len...@felloff.net wrote:
cinap_len...@felloff.net writes:
> > The firmware on a pi4 with 2GB or 4GB RAM will only report 1GB.
> > I believe you need to look at the board id (or probe for invalid
> > addresses as in the teg2 kernel) to find out the real amou
On Wed, 21 Aug 2019 21:53:42 +0200 cinap_len...@felloff.net wrote:
cinap_len...@felloff.net writes:
> thank you!
>
> i believe its just starting rio so you dont get any more output.
>
> interestingly, the framebuffer was set up without error as
> far as the kernel is concerned. otherwise we would g
> The device tree has two entries.
>
> offset:0
> lenght:0x3c40
>
> offset:0x4000
> length:0xbc00
excellent! that explains it.
--
cinap
new kernel that should be able to deal with the two regions:
http://felloff.net/usr/cinap_lenrek/9pi4
sha1sum:
0222a824ec04c672955560ea120fa4d8de848e79
--
cinap
On Thu, 22 Aug 2019 01:58:39 +0200 cinap_len...@felloff.net wrote:
> new kernel that should be able to deal with the two regions:
>
> http://felloff.net/usr/cinap_lenrek/9pi4
>
> sha1sum:
>
> 0222a824ec04c672955560ea120fa4d8de848e79
cat '#ec/*maxmem'
0x3e60 0x4000 0xfc00
Ethernet and
18 matches
Mail list logo
