Re: i2c devices on TSC
Jason Thorpe <[email protected]> Tue, 17 Feb 2026 09:40:16 -0500
| Newsgroups | gmane.os.netbsd.ports.alpha |
|---|---|
| Message-ID | <[email protected]> |
> On Feb 17, 2026, at 9:15=E2=80=AFAM, Jason Thorpe <[email protected]> = wrote: >=20 >=20 >=20 >> On Feb 17, 2026, at 8:16=E2=80=AFAM, Julian Coleman = <[email protected]> wrote: >>=20 >> Hi, >>=20 >>> Oh, I forgot to mention, this configuration gets the snot beat out = of it on jklos=E2=80=99s DS25: >>>=20 >>> https://dmesgd.nycbug.org/dmesgd?do=3Dview&id=3D7447 >>=20 >> This reminded me: >>=20 >> [ 1.000000] tsciic0 at tsc0 >> [ 1.000000] iic0 at tsciic0: I2C bus >>=20 >> that a long time back, I added the tsciic driver and also entries in >> GENERIC for the devices on the DS20L. However, as the entries are >> commented out, I guess that almost no-one uses them. I wonder if = there >> is a nice way to add them at run time, because we already know the >> machine model. >=20 > Yup. Do you have a dmesg from a DS20L with these devices enabled? Ah, but there=E2=80=99s one enhancement to be made. spdmem, well, not = all of those will be present, and we don=E2=80=99t want to see =E2=80=9Cno= t configured=E2=80=9D messages for the ones not there. I=E2=80=99ll = mull it over. A flag indicating =E2=80=9Cdiscover=E2=80=9D is probably = in order. -- thorpej