Re: Objective of OpenWRT/x86?

2023-05-04 Thread Joseph Mullally
On Thu, May 4, 2023 at 7:35 AM Elliott Mitchell wrote: > On Thu, May 04, 2023 at 03:50:05AM +0100, Daniel Golle wrote: > > On Wed, May 03, 2023 at 06:36:10PM -0700, Elliott Mitchell wrote: > > > On Tue, May 02, 2023 at 02:45:43AM +0200, Alberto Bursi wrote: > > > > On 26/04/23 22:17, Elliott Mitch

Re: Objective of OpenWRT/x86?

2023-05-01 Thread Joseph Mullally
On Mon, May 1, 2023 at 5:43 AM Philip Prindeville wrote: >> On Apr 28, 2023, at 11:18 PM, Elliott Mitchell wrote: >>> On Fri, Apr 28, 2023 at 12:04:15PM -0600, Philip Prindeville wrote: >>> Um... you can't "virtualize" WiFi in any VM I've ever seen. >> >> You can though pass PCIe devices to a VM

Re: Objective of OpenWRT/x86?

2023-04-28 Thread Joseph Mullally
As you point out elsewhere, this "optional builtin modules" problem is typically solved with bootstrapping initrd images. But adding something like initramfs-tools or dracut into OpenWrt would be over complicating things, since the current x86/64 images seem to suit everyone. _

Re: Objective of OpenWRT/x86?

2023-04-28 Thread Joseph Mullally
On Sat, Apr 29, 2023 at 3:29 AM Elliott Mitchell wrote: > I'm looking at the list of built-in drivers and seeing many which > will perhaps only be used by 25% of installations. That figure seems hypothetical, but you would propose to break 25% of users installations for insignificant memory reduc

Re: Objective of OpenWRT/x86?

2023-04-26 Thread Joseph Mullally
One nice feature for users of the "x86/64" and similar builds are that they work out of the box on most generic hardware or virtualization platforms. I use it on real hardware and KVM with device passthrough, and it was very easy to set up. I'm guessing this is far more common than speculative high

Re: next OpenWrt 22.03 and 21.02 minor release

2023-03-29 Thread Joseph Mullally
On Tue, Mar 28, 2023 at 11:44 AM Paul Spooren wrote: > > > > How should simple github PRs that are intended be applied to both > > /master and /openwrt-22.03 be handled? > > Feel free to open both at the same time to have the CI running, however be > sure to mark the backport as “draft” and once

Re: next OpenWrt 22.03 and 21.02 minor release

2023-03-28 Thread Joseph Mullally
> If we should backport more changes please create a pull request on > github, send a patch with the 22.03 or 21.02 prefix to the mailing list > or send a mail with a link to the master commit we should backport as an > answer to this mail and I will have a look at the commit. How should simple gi

GitHub mirror for firmware-utils Inbox

2022-11-14 Thread Joseph Mullally
Hi all, Can a GitHub mirror be created for https://git.openwrt.org/project/firmware-utils.git ? It seems every major part of the project already has one: https://openwrt.org/submitting-patches#deciding_where_to_send_the_patch Some time ago firmware-utils was split from the main repo. Some device

Re: Seperating firmware-utils into seperate repo

2022-04-12 Thread Joseph Mullally
> Most in-house OpenWrt packages are actually stored in their > own git repo, see https://git.openwrt.org/ down in the > /project/something_something.git > > -Alberto Thanks for the good suggestions Alberto. I still think it will be a messy process for most new device contributors (where a lot of

Patch: ath79: Move TPLink WPA8630Pv2 to tiny target

2022-04-08 Thread Joseph Mullally
https://github.com/openwrt/openwrt/pull/4500#issuecomment-1090822176 Old patch that may not be visible on the recent PRs. > These devices only have 6MiB available for firmware, > which is not enough for recent release images, so > move these to the tiny target. Tested by others and reviewed, sho

Seperating firmware-utils into seperate repo

2022-03-13 Thread Joseph Mullally
Hi, firmware-utils was separated from openwrt.git into its own repository a few months ago: https://git.openwrt.org/?p=project/firmware-utils.git https://github.com/openwrt/openwrt/commit/8cc9a74a3f6bf363645efda6db417f8dadd3d844 If it's going to stay separate, it looks like these changes are stil

ucidef_set_led_netdev port_mask equivilant for DSA?

2022-03-12 Thread Joseph Mullally
Hi, I'm working on a DSA device where the OEM behaviour has 1 Ethernet LED show the state of 3 Ethernet switch ports (and is off when none of them are active). It looks like "ucidef_set_led_netdev" is the main way of setting LEDs for DSA switches. Is there an equivilant for the "port_mask" argumen

Re: Custom DTS / DTB building with ImageBuilder

2021-03-09 Thread Joseph Mullally
e which patches in a new custom device profile and builds it: [1] https://github.com/jwmullally/openwrt_wpa8630p_v2_fullmem/blob/master/Makefile On Sat, Feb 27, 2021 at 12:21 AM Joseph Mullally wrote: > > Hi, > > Device Tree is great as it decouples the hardware layout from the > kernel b

Custom DTS / DTB building with ImageBuilder

2021-02-26 Thread Joseph Mullally
Hi, Device Tree is great as it decouples the hardware layout from the kernel build. What are peoples thoughts on supporting custom DTS building in ImageBuilder? There are a few advantages: Uses the official kernel, makes it easier to support out-of-tree unofficial firmwares etc. [1] says DTS files