Re: VIA Padlock on AMD64

[Andrius V <vezhlys%gmail.com@localhost>]

On Tue, Jul 21, 2020 at 12:31 AM Taylor R Campbell <riastradh%netbsd.org@localhost> wrote:
>
> > Date: Tue, 21 Jul 2020 00:16:16 +0300
> > From: Andrius V <vezhlys%gmail.com@localhost>
> >
> > After a bit more investigation, yes, it is kassert (kernel diagnostic
> > assertion "viadrm_pci_ids[i].subvendor == PCI_ANY_ID" ), doesn't
> > matter amd64/i386.
>
> Panic should be fixed in via_pci 1.3.
>

Thank you for the quick fix. It works.

I agree regarding padlock that it is not useful. On the other hand,
viadrmums driver potentially can be useful as a module for amd64
platform, since (at least) the first generation of VIA Nano based
boards used some supported chipset graphics, for example the one in
CN896 chipset (don't have hardware to test though) and driver is
disabled in GENERIC by default.

>
> Can you share dmesg?
>

Portion of dmesg related to viadrmums once I included VX900 ID
(haven't tested VX800): {0x1106, 0x7122, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
VIA_DX9_0}:

[   1.2754981] vga0 at pci0 dev 1 function 0: VIA Technologies VX900
Graphics [Chrome9 HD] (rev. 0x00)
[   1.2754981] wsdisplay0 at vga0 kbdmux 1
[   1.2754981] wsmux1: connecting to wsdisplay0
[   1.2754981] viadrmums0 at vga0pci_mem_find: void region
[   1.2754981] pci_mem_find: void region
[   1.2754981] pci_mem_find: void region
[   1.2754981] pci_mem_find: void region
[   1.2754981] viadrmums0: map 3 failed
[   1.2754981] pci_mem_find: void region
[   1.2754981] viadrmums0: map 4 failed
[   1.2754981] pci_mem_find: void region
[   1.2754981] viadrmums0: map 5 failed
[   1.2754981] DRM debug in drm_minor_register:
[   1.2754981] DRM debug in drm_minor_register:
[   1.2754981] DRM debug in drm_minor_register:
[   1.2754981] DRM debug in drm_minor_register: new minor registered 0
[   1.2754981] kern info: [drm] Supports vblank timestamp caching Rev
2 (21.10.2013).
[   1.2754981] kern info: [drm] No driver support for vblank timestamp query.

Not sure how useful to work on this though. Linux doesn't seem to have
newer graphics IDs in VIA DRM driver too (possibly abandoned over new
effort?). Currently Xorg server starts on VX900, but screen complains
with "Input signal is out of range" error with or without viadrmums
driver, so I can't see anything on the screen (maybe I need some
manual xorg configuration). I don't remember if it was the case
before, I usually used console only.

Unrelated, but I think it appeared pretty recently in dmesg logs and
related to your changes:
[   4.0518619] aes: VIA ACE
....
[  11.7018582] cpu_rng via: failed repetition test
T[  12.4718583] entropy: ready

Before it was:
cpu_rng: VIA
rnd: seeded with 256 bits

> Do you have any older 32-bit VIA hardware to compare to see whether it
> works better there?  (Haven't tried it on my 32-bit VIA laptop in a
> while, and right now it's too hot to power that little space heater
> on!)

Yes, I do have an old 2xVIA Eden-N based board with CN400 chipset. The
driver was working pretty well on it (tested relatively recently).