Re: Ethernet switch with linux/openwrt and DSA

2023-04-04 Thread Greg Oliver
On Tue, Apr 4, 2023 at 9:45 AM Greg Oliver  wrote:
>
> On Mon, Apr 3, 2023 at 5:11 PM Michael Richardson  wrote:
> >
> >
> > Janusz Dziedzic  wrote:
> > >> > Finally buy: D-LINK DGS-1210-48 G1.
> > >>
> > > Also - HP 1920-24G JG924A works correctly.
> >
> > > But what about future? Is there any new device we can buy and use
> > > openwrt there?  Or even 2.5Gbps/5Gbps?
> >
> > > So far just buy used/older devices.
> >
> > mcr> Is this a device that is still for sale?  I have some control plane
> > mcr> things that I'd like to test on a variety of switches.  I using the
> > mcr> Zyxel GS1900 now.
> >
> > My testing is way behind.
> >
> > > ZyXEL GS1900-48-EU0102F (new one) will be also fine?
> >
> > Assuming it boots openwrt, more ports is more interesting to me than faster 
> > ports.
>
> I have a handful of GS1900-8HP models I would like to try this out on,
> but the images are not where previously mentioned.  Get a 404 and only
> 4 chipsets are listed under the RealTek nightly directory.  Any idea
> where I can currently find them?
>
> TiA!

NM - I found it - sorry for the noise!

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Ethernet switch with linux/openwrt and DSA

2023-04-04 Thread Greg Oliver
On Mon, Apr 3, 2023 at 5:11 PM Michael Richardson  wrote:
>
>
> Janusz Dziedzic  wrote:
> >> > Finally buy: D-LINK DGS-1210-48 G1.
> >>
> > Also - HP 1920-24G JG924A works correctly.
>
> > But what about future? Is there any new device we can buy and use
> > openwrt there?  Or even 2.5Gbps/5Gbps?
>
> > So far just buy used/older devices.
>
> mcr> Is this a device that is still for sale?  I have some control plane
> mcr> things that I'd like to test on a variety of switches.  I using the
> mcr> Zyxel GS1900 now.
>
> My testing is way behind.
>
> > ZyXEL GS1900-48-EU0102F (new one) will be also fine?
>
> Assuming it boots openwrt, more ports is more interesting to me than faster 
> ports.

I have a handful of GS1900-8HP models I would like to try this out on,
but the images are not where previously mentioned.  Get a 404 and only
4 chipsets are listed under the RealTek nightly directory.  Any idea
where I can currently find them?

TiA!

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Question re DeviceTree addressing

2023-04-04 Thread Caleb James DeLisle

Thank you very much, that clears things up a lot.

Thanks,
Caleb

On 04/04/2023 05:33, Florian Fainelli wrote:



On 4/3/2023 7:00 AM, Caleb James DeLisle wrote:

Hello folks,

I've been working on trying to port an en7526 and in doing so I'm trying to learn how to at least 
partially write a DTS file from an old style header full of #defines.


I ran into a bit of a quandry, I'm comparing the mt7621.dtsi file to an older MT7621 memory map 
header:


https://github.com/openwrt/openwrt/blob/master/target/linux/ramips/dts/mt7621.dtsi#L100

https://github.com/keenetic/kernel-49/blob/master/arch/mips/include/asm/rt2880/rt_mmap.h#L48

```
 palmbus: palmbus@1e00 {
 compatible = "palmbus";
 reg = <0x1e00 0x10>;
 ranges = <0x0 0x1e00 0x0f>;

[...]

 i2c: i2c@900 {
 compatible = "mediatek,mt7621-i2c";
 reg = <0x900 0x100>;
```

For me, means there should be an I2C controller mapped at address 0x1e000900.


Correct.



But looking at rt_mmap.h I see:

```
#define RALINK_I2C_BASE    0xBE000900
```

And in fact almost everything is based on 0xBE00, except UART and USB addresses which are 
"correct". And I see these 0xBE00 addresses being passed through KSEG1ADDR() so it seems they 
are physical memory addresses, not virtual.


KSEG1ADDR does a logical or so it would not be altering RALINK_I2C_BASE when OR'd with 0xa000 
(KSEG1) you would still get 0xBE000900.


It seems to me like in places where it may be necessary to pass a physical address they used 
physical addresses such that ioremap() ends-up returning a proper kernel virtual address in KSEG1, 
however everywhere else the driver might have just directly de-referenced the constant which ends-up 
working just fine as well.


HTH


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: irt: tools/squashfs4: enable parallel builds

2023-04-04 Thread Paul Oranje via openwrt-devel
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.

To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---


> Op 3 apr. 2023, om 23:23 heeft Elliott Mitchell  het 
> volgende geschreven:
> 
> On Mon, Apr 03, 2023 at 09:43:28PM +0800, 刘林辉 wrote:
>> The reason may be that my computer is under high load all the time.
>> 
>> So I wrote a simple workflow to test squashfs4 using github actions
>> https://github.com/lovehackintosh/Actions-OpenWrt/actions/runs/4597175958.
> 
> Okay, I can believe that.  Just an issue that it made the commit message
> misleading.  Parallel building *can* slow things down.  `squashfs4` does
> look a bit risky for that since most of its source is in 3 files and
> everything else is tiny.
> 
> Might want to ensure your background jobs have been run via `nice` or
> run `renice` on them later.  This makes benchmarks better guides.
> 
> 
> 
> On Mon, Apr 03, 2023 at 09:12:47PM +0200, Paul Oranje wrote:
>> 
>>> Op 3 apr. 2023, om 00:28 heeft Elliott Mitchell  het 
>>> volgende geschreven:
>>> 
>>> Am I the only person who finds commit 3efd49a588
>> Cannot find that one, but have you seen 
>> 82e1f041f9a6cf9232c9f73938ef3b11c34cca0f ?
>> 
> 
> 3efd49a588 is about allowing the build process of `squashfs4` to use
> multiple processors.  Whereas 82e1f041f9 is about allowing `squashfs4`
> to use multiple processors during its runtime.  Thus these two do not
> conflict and do make sense together.
> 
> (FYI `git rev-parse --short 82e1f041f9a6cf9232c9f73938ef3b11c34cca`)
Ah, I should have looked better. Thanks

> 
> 
> -- 
> (\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
> \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
>  \_CS\   |  _  -O #include  O-   _  |   /  _/
> 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
> 
> 
> 
> 
> 
> 
> -- 
> (\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
> \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
>  \_CS\   |  _  -O #include  O-   _  |   /  _/
> 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
> 
> 
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel



--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel