Re: gpib_bitbang: problem with GPIO tables

dave penkler <[email protected]> Tue, 3 Sep 2024 17:00:04 +0200
Newsgroups gmane.linux.hardware.gpib.general
Message-ID <CAL=kjP1tKy5tDYL+E5b7rbDDR-rNP3RVjVhd+-Z4QNzDcMkz=g@mail.gmail.com>
Hi Michael,
Yes that is normal - your Pi3 is probably based on a bcm2710 SoC which has
the same line-names as Pi4/5.
Raspberry Pi made a couple of Pi3 variants based on different SoCs. The
table labelled p3 is for the bcm2387 variant.
I should change the names of the table variables to be just 0,1 and 2 to
avoid confusion.
cheers,
-Dave

On Wed, 28 Aug 2024 at 19:00, Michael Schwingen <[email protected]>
wrote:

> On 28.08.24 15:37, dave penkler wrote:
> > Hi,
> > The tables come from the different RPi device trees. Earlier Pi3A+,
> > Pi3B+ based on bcm2837 had the same DT as Pi2B based on bcm2836 but
> > with gpio14 and 15 called TXD1 and RXD1 instead of TXD0 and RXD0 as
> > for the Pi2B. The bcm2710 and bcm2711 are all like table index 2. As
> > we have no clean way to test what system we are running on we try the
> > three different tables from the oldest to newest.
>
> That approach works fine for me - however, it feels strange that the Pi3
> uses the Pi4/5 table, while the attempt to use the Pi3 table fails.
>
> Is that normal?
>
>
> cu
>
> Michael
>
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general