Hello Mark, tech@,
since A64 now supports dynamic frequencies and thermal zones I thought
I could go back to sxisid driver idea.
Device tree excerpts:
&{/soc} {
ths: thermal_sensor@1c25000 {
compatible = "allwinner,sun50i-a64-ths";
reg = <0x01c25000 0x100>;
> Date: Sun, 29 Sep 2019 21:25:11 +0200
> From: Krystian Lewandowski
>
> Hello Mark, tech@,
> since A64 now supports dynamic frequencies and thermal zones I thought
> I could go back to sxisid driver idea.
>
> Device tree excerpts:
>
> &{/soc} {
> ths: thermal_sensor@1c25000 {
>
Mark, thank you for quick feedback.
I'm not pushing or anything of course,
just want to provide more information.
I put radiator on A64+ I'm using (both were tested with radiator),
also FreeBSD and OpenBSD may have been using different clocks
(648MHz vs 768MHz), original mail was sent in April, l
i got an email recently asking how to configure the tunnel identifier
on an eoip(4) interface, and initially wanted to point the sender
at the manpage. unfortunately, the manpage is written for programmers
who have spent a lot of time in network drivers, ie, me. everyone
else who just wants to conf
the "public" bpf api no longer supports custom copy functions, so we can
remove the plumbing for it internally in the bpf code.
ok?
Index: bpf.c
===
RCS file: /cvs/src/sys/net/bpf.c,v
retrieving revision 1.180
diff -u -p -r1.180 bpf.
On Mon, Sep 30, 2019 at 10:28:50AM +1000, David Gwynne wrote:
> i got an email recently asking how to configure the tunnel identifier
> on an eoip(4) interface, and initially wanted to point the sender
> at the manpage. unfortunately, the manpage is written for programmers
> who have spent a lot of
On Mon, Sep 30, 2019 at 12:06:34PM +1000, David Gwynne wrote:
> the "public" bpf api no longer supports custom copy functions, so we can
> remove the plumbing for it internally in the bpf code.
>
> ok?
>
> Index: bpf.c
> ===
> RCS fi
