Only two patches against mainline remains. Switch to v5.10
which works very nicely with all Gemini devices.
Signed-off-by: Linus Walleij
---
target/linux/gemini/Makefile | 2 +-
target/linux/gemini/config-5.10 | 465 ++
...t-fotg2-add-Gemini
t" simply.
I am unsure about the procedure to test it though, also I always get a
bit confused about how these configs are even generated.
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
This makes no sense on anything but the IXP4xx platform
that we do not even support anymore. If we bring it back,
it can be selectively enabled for that platform only.
Signed-off-by: Linus Walleij
---
target/linux/generic/config-5.10 | 1 +
1 file changed, 1 insertion(+)
diff --git a/target
This config is for platforms that have:
A) CONFIG_THERMAL set (we disable it by default)
B) Has thermal zones that need to control cpufreq
This is not suitable for default config, it needs to be enabled
on a per-target basis in individual configs.
Signed-off-by: Linus Walleij
---
target/linux
We do not enable GPIO_CDEV so do not enable CDEV_V1
either. As we rebuild the whole userspace and kernel
in OpenWRT it doesn't make any sense to support the
old ABI anyway: the new one should be used by default.
Signed-off-by: Linus Walleij
---
target/linux/generic/config-5.10 | 1 +
1
blk*[0-9]|mspblk*[0-9]|sd*[!0-9]|sr*", \
ATTR{queue/scheduler}="bfq"
We are not using udev so we need a similar rule in a
similar patch for procd, or we can patch the kernel to
use BFQ by default if we do not expect people to use
OpenWRT with enterprise storage arrays.
Signed-off-b
OpenWRT is used as a base for embedded products for the
future market it is the right default to set.
Several targets enable this selectively, probably some of
them should consider disabling it and see what happens.
Cc: Arnd Bergmann
Signed-off-by: Linus Walleij
---
target/linux/generic/config-5.10
This CMA memory allocation option only applies to NUMA
(Non-Uniform Memory Access) systems which are seldom
the kind of systems that OpenWRT address.
It is safe to assume that any system that need this
option would turn it on locally.
Signed-off-by: Linus Walleij
---
target/linux/generic
On Thu, Apr 15, 2021 at 12:45 AM Rosen Penev wrote:
> On Wed, Apr 14, 2021 at 4:46 AM Linus Walleij
> wrote:
> > The new multiqueue block layer has an IO scheduler named
> > BFQ (Budget Fair Queue) that is suitable for slow
> > single-queue block devices such as (S)A
7952f848ecba
Aha I didn't know there was a package for it, nice. Then I would only
need to patch some rules into that package which is more of a local
change.
Thanks!
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.
27;s a bummer. I was certain it was migrated...
Let's hold this off then.
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
The non-MQ CFQ, deadline and noop IO schedulers are
deleted from the Linux kernel
since commit f382fb0bcef4c37dc049e9f6963e3baf204d815c
"block: remove legacy IO schedulers".
Signed-off-by: Linus Walleij
---
target/linux/generic/config-5.10 | 4
1 file changed, 4 deletions(-)
di
all kernel modules
> activated is helpful. You can do it by activation CONFIG_ALL_KMODS=y in
> the OpenWrt configuration. This is what the build bot uses:
> https://downloads.openwrt.org/snapshots/targets/gemini/generic/config.buildinfo
OK building that now... thank
ost to device tree.
Now that I know there is interest I might get more motivation to
work on it :) can I include you on CC if I post patches for
review?
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.open
eviews
> and testing on devices as time permits. I have about 30 different IXP4xx
> devices available in my collection.
Fair enough, I pulled out my Cambria yesterday to continue some of the
work. I will include you on Cc for patches I send so you know what is
happening.
Yo
Only two patches against mainline remains. Switch to v5.10
which works very nicely with all Gemini devices.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Update the config-5.10 using the proper oldconfig
update target.
- Drop config options that have been migrated to the
target/li
The D-Link DIR-685 has a small screen with a framebuffer
console, so if we have this, when we start, display the
banner on this framebuffer console so the user know they
are running OpenWRT as root filesystem.
Signed-off-by: Linus Walleij
---
This is nice on any routers with a screen. OK I guess
Hi,
I was trying to add a Technicolor router to the wiki here:
https://wiki.openwrt.org/meta/create_new_dataentry_page
But Technicolor does not exist in the Brand list. A previous
entry uses Thomson but that is their old name.
Can someone here add Technicolor to the brand list?
Yours,
Linus
Looping in tmo26, as mentioned at the page. Mea culpa.
Yours,
Linus Walleij
On Tue, May 31, 2016 at 11:28 PM, Linus Walleij
wrote:
> Hi,
>
> I was trying to add a Technicolor router to the wiki here:
> https://wiki.openwrt.org/meta/create_new_dataentry_page
>
> But Technico
like this: if the kernel entity size
gets silly big (bigger than the flash memory) we are
probably using the wrong endianness.
Example: my kernel of 0x0067ff64 was switched around by
wrong endianness and detected as 0x64ff67a0 (the actual
size in swapped endianness + header 0xa0).
Signed-off
he DIR-685
from stock firmware using the web UI and the serial console
boot loader.
Signed-off-by: Linus Walleij
---
target/linux/gemini/config-4.14 | 2 +
target/linux/gemini/config-4.19 | 2 +
target/linux/gemini/image/Makefile| 23 +++-
...emini-Indent
526"
CONFIG_arm=y
CONFIG_ARCH="arm"
CONFIG_SOFT_FLOAT=y
Any hints?
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
g
this patch a mere make menuconfig && make clean && make will not
do it, you have to rm -rf build_dir.
After I did this and rebuilt the whole universe overnight it works
again, so I am happy now! :D
Thanks for your help anyway!
Yours,
Linus Walleij
_
This makes sysupgrade work on the D-Link DIR-685 after
initial factory install.
We create the platform.sh script to support sysupgrade
on more targets as we move on with sysupgrade support.
Signed-off-by: Linus Walleij
---
.../gemini/base-files/lib/upgrade/platform.sh | 54
This makes sysupgrade work on the D-Link DIR-685 after
initial factory install.
We create the platform.sh script to support sysupgrade
on more targets as we move on with sysupgrade support.
Cc: Petr Štetiar
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Append metadata to sysupgr
On Tue, May 14, 2019 at 10:30 AM Petr Štetiar wrote:
> Linus Walleij [2019-05-12 21:13:17]:
> > +REQUIRE_IMAGE_METADATA=1
>
> once you set this, you don't need to check for the image magic, do you? If so,
> please provide the reason for that.
The image magic is necess
[Adding Stijn Tintel as DAP-2695 A1 maintainer, I think he want to
know how we solve this.]
On Tue, May 14, 2019 at 2:07 PM Petr Štetiar wrote:
> Linus Walleij [2019-05-14 13:16:50]:
> > On Tue, May 14, 2019 at 10:30 AM Petr Štetiar wrote:
> >
> > > Linus Walle
his works around the problem of the machine not booting
after factory install unless the sysupgrade is applied
immediately.
Based on commit e3875350f3e4185020b64e0588bba521cd1d6e64
"ar71xx: add support for D-Link DAP-2695 rev. A1"
Cc: Stijn Tintel
Signed-off-by: Linus Walleij
---
p
correct.
The magic number is always stored in little endian
format however, so make sure this is always read
in LE32 format. I chose to create a straight-forward
le32_to_cpu() static inline that IMO is simple and
easy to read.
Cc: Stijn Tintel
Signed-off-by: Linus Walleij
---
It'd be gre
This makes sysupgrade work on the D-Link DIR-685 after
initial factory install.
We create the platform.sh script to support sysupgrade
on more targets as we move on with sysupgrade support.
Cc: Petr Štetiar
Signed-off-by: Linus Walleij
---
ChangeLog v2->v3:
- Drop the WRGG magic check: af
you can chime
in on how you want people to do generic checksum etc.
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
] mount_root: reading rootfs failed
[ 25.726426] mount_root: mounting /dev/root
Well that is not very strange since the whole firmware partition
is made read-only in the device tree. Let's fix that by augmenting
the OpenWrt patch.
Signed-off-by: Linus Walleij
---
...-DIR-685-partition-tabl
_NET_DSA_TAG_DSA is not set
> # CONFIG_NET_DSA_TAG_EDSA is not set
> +# CONFIG_NET_DSA_VITESSE_VSC73XX is not set
Adds them to the generic config as "not set" (disabled).
It seems this needs to be partially reverted for Gemini to work
The DNS-313 isn't the only special board so let's bite the
bullet and create a case ladder in preparation for DIR-685.
Signed-off-by: Linus Walleij
---
.../lib/preinit/05_set_ether_mac_gemini | 30 ---
1 file changed, 19 insertions(+), 11 deletions(-)
diff --gi
hexdump.
Signed-off-by: Linus Walleij
---
.../linux/gemini/base-files/lib/preinit/05_set_ether_mac_gemini | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/gemini/base-files/lib/preinit/05_set_ether_mac_gemini
b/target/linux/gemini/base-files/lib/preinit/05_set_et
The DIR-685 has the MAC addresses in the RedBoot code just like
DNS-313. Check some magic numbers to determine that the MAC
address is where we want it and extract it from RedBoot.
Signed-off-by: Linus Walleij
---
.../lib/preinit/05_set_ether_mac_gemini | 15 +++
1 file
On Sun, May 26, 2019 at 11:46 PM Hauke Mehrtens wrote:
> On 5/24/19 11:09 PM, Linus Walleij wrote:
> > Hi Hauke,
> >
> > this patch regresses my Gemini systems because I really need these switches
> > to come up and this patch:
>
> Sorry Linus,
>
> I didn
ot;ip link set dev eth0 address $MAC1"
Testing this:
ip link set eth0 address 00:50:c2:11:11:11
ip: socket(AF_PACKET,2,0): Address family not supported by protocol
Any hints? According to the help it should work ...
Yours,
Linus Walleij
___
openwr
This simplifies the ethernet address extraction script
by using standard library functions to locate the MTD
partitions and extract ethernet address from a binary
offset location in the flash.
Suggested-by: Christian Lamparter
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- New pa
The DIR-685 has the MAC addresses in the RedBoot code just like
DNS-313. Check some magic numbers to determine that the MAC
address is where we want it and extract it from RedBoot.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Rebase on the other patches
- Use library functions to
The DNS-313 isn't the only special board so let's bite the
bullet and create a case ladder in preparation for DIR-685.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Rebase on the new patch using library functions
---
.../lib/preinit/05_set_ether_mac_gemi
] mount_root: reading rootfs failed
[ 25.726426] mount_root: mounting /dev/root
Well that is not very strange since the whole firmware partition
is made read-only in the device tree. Let's fix that by augmenting
the OpenWrt patch.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Refresh the
One of the patches were not properly refreshed. Fix it up.
Signed-off-by: Linus Walleij
---
.../0008-ARM-dts-Enable-Gemini-flash-access.patch | 7 ---
1 file changed, 7 deletions(-)
diff --git
a/target/linux/gemini/patches-4.19/0008-ARM-dts-Enable-Gemini-flash-access.patch
b
On Tue, Jun 11, 2019 at 11:28 PM Linus Walleij wrote:
> One of the patches were not properly refreshed. Fix it up.
>
> Signed-off-by: Linus Walleij
Bah, drop this patch. I was fixing my own out-of-tree patches :P
Sorry for the buzz
Linu
://git.openwrt.org/?p=openwrt/staging/chunkeey.git;a=commit;h=b106a522001e970378c38279fe598acbc867d0f4
>
> Let me know if this works now with the ip tool.
Yes! I applied this series and all comes up nicely, right MAC address
and writeable root filesystem. Feel free to push this and thanks so
much
an you try this patch, if this solves the problem I will commit
it upstream as well:
>From ce4b6db51658e0954f97837095393c5fd1416db2 Mon Sep 17 00:00:00 2001
From: Linus Walleij
Date: Sat, 15 Jun 2019 10:18:48 +0200
Subject: [PATCH] gpio: ath79: Clear pending IRQs
The ath79 gpio driver may emit
It's a simple typo in the DNS file, which was pretty serious.
No scripts were working properly. Fix it up.
Signed-off-by: Linus Walleij
---
arch/arm/boot/dts/gemini-dlink-dns-313.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/gemini-dlink-dns-31
t
eads zero for the requested IRQ:
while (ath79_gpio_read(ctrl, AR71XX_GPIO_REG_INT_PENDING) & mask) {}
This way we wait for the status to go low before we allow any IRQs to
fire after enableing.
Maybe not so good since we may want to turn on IRQs that are asserted
at some point, but worth a try.
Yours,
Linus Wal
really like the second idea as dropping interrupts without feedback
> is probably not
> what we want.
I think it makes a lot of sense on mechanical pushbuttons to
implement generic debounce.
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On Tue, Jun 18, 2019 at 12:53 PM David Bauer wrote:
> On 17.06.19 22:26, Linus Walleij wrote:
> > I think it makes a lot of sense on mechanical pushbuttons to
> > implement generic debounce.
>
> This is, however, not the job of the GPIO driver or is it?
If the GPIO bl
The DIR-685 needs this module compiled in for safety
(it is facing the LAN ports) and it is now (as of
kernel v4.19) using the DSA switch architecture so
swconfig is not needed.
Signed-off-by: Linus Walleij
---
target/linux/gemini/image/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git
This adds image generation for the StorLink reference design
SL93512r. This board is now supported upstream in kernel
v4.19.
As this image structure is identical to SQ201 and Raidsonic,
we simply refer to this as "storlink-reference" from now on.
Signed-off-by: Linus Walleij
---
ta
>
> @Linus: Can you please make a patch that adds the missing file?
Yep I made a patch, testing it as we speak.
Sorry for stupid mistakes, I guess I forgot some git add and
then rebased and lost the file.
Yours,
Linus Walleij
___
openwrt-devel
Somehow I missed to add the magical image cooking file
for the SL93512r. Fix it.
Reported-by: Christian Lamparter
Signed-off-by: Linus Walleij
---
.../gemini/image/ImageInfo-storlink_sl93512r | 18 ++
1 file changed, 18 insertions(+)
create mode 100644 target/linux/gemini
changing
baudrate between boot loader and kernel. The setting in the
device tree corresponds to what the boot loader is using.
Signed-off-by: Linus Walleij
---
target/linux/gemini/config-4.14 | 2 --
target/linux/gemini/config-4.19 | 2 --
2 files changed, 4 deletions(-)
diff --git a/target/linux
WAN
and the LAN ports share the same ethernet CPU port
the ethernet port should not be part of either WAN or
LAN.
Signed-off-by: Linus Walleij
---
.../gemini/base-files/etc/board.d/02_network | 25 +++
1 file changed, 25 insertions(+)
create mode 100755 target/linux/gemini/base
On Fri, Jul 12, 2019 at 8:57 AM Hauke Mehrtens wrote:
> On 7/12/19 8:07 AM, Linus Walleij wrote:
> > + # These are all connected to eth1 thru VSC7385
> > + ucidef_set_interfaces_lan_wan "eth1 lan1 lan2 lan3 lan4" "eth0"
>
> This will create a br
ocumentation/networking/dsa/configuration.rst
Oh that is really good documentation. I linked it in the Ethernet switch
page in the OpenWrt wiki.
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ned-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Remove the eth1 from the LAN bridge in both the
Vitesse switch devices, instead bring up each ethernet
master interface independently with "none" protocol.
---
.../gemini/base-files/etc/board.d/02_network | 27
terface "eth" ifname "eth0" protocol "none"
ucidef_set_interfaces_lan "lan1 lan2 lan3 lan4"
If you don't have any WAN interface (uplink) on the device.
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On Sun, Jul 14, 2019 at 10:46 PM Linus Walleij wrote:
> On Sun, Jul 14, 2019 at 5:15 PM Pawel Dembicki
> wrote:
>
> > > +storlink,gemini324)
> > > + # These are all connected to eth1 thru VSC7385
> > > + ucidef_set_interfac
Upstream patch fixing the errors in the device tree.
Signed-off-by: Linus Walleij
---
...-gemini-Fix-up-confused-pin-settings.patch | 54 +++
1 file changed, 54 insertions(+)
create mode 100644
target/linux/gemini/patches-4.19/0024-ARM-dts-gemini-Fix-up-confused-pin
The SL93512r and the NAS4220B have Redboot partition
tables (rely on these) and need to boot from mtdblock3.
Add two patches from upstream to fix this.
Signed-off-by: Linus Walleij
---
...-Switch-to-redboot-partition-parsing.patch | 104 ++
...dts-gemini-Mount-root-from
-by: Linus Walleij
---
.../linux/gemini/image/copy-kernel/.gitignore | 1 +
.../linux/gemini/image/copy-kernel/Makefile | 32 +
.../gemini/image/copy-kernel/copy-kernel.S| 45 +++
3 files changed, 78 insertions(+)
create mode 100644 target/linux/gemini/image
flash these manually using the native boot
loader PLATO, "Y" alternative for the zImage, "R" for
the rd.gz image and "A" for hddapp.tgz.
This works fine and I can now boot to prompt on the SQ201
with nothing but flash.
Signed-off-by: Linus Walleij
---
target/linu
rt also has this switch:
https://openwrt.org/toh/evaluation.boards/pb44
with a custom driver:
https://github.com/openwrt/openwrt/blob/master/target/linux/ar71xx/files/drivers/spi/spi-vsc7385.c
It's a MIPS device though, and I don't know if anyone is
actively maintaining it and could test to
On Wed, Jul 17, 2019 at 7:23 PM Linus Walleij wrote:
> This package just contains a small Gemini-only assembler
> bootstrap loop to copy the kernel from the two fragments
> (previously zImage at 0x0160 and initramdisk at 0x0080)
> into one big zImage of up to 8 MB at 0x0040
explanation of what the 8 different IO modes may be.
Set it to zero for the time being and drop a comment so
people know what is going on if they run into trouble. This
"mode zero" works fine with the D-Link DIR-685 with
RTL8366RB.
Signed-off-by: Linus Walleij
---
drivers/net/dsa/rtl836
from the switch chip.
Cc: Antti Seppälä
Cc: Roman Yeryomin
Cc: Colin Leitner
Cc: Gabor Juhos
Cc: Florian Fainelli
Signed-off-by: Linus Walleij
---
ChangeLog RFCv2->v1
- Correct the PHY power save register from 0x21 to 0x15
as it should be.
- Drop the comment about the DSA switch.
- Use
On Tue, May 29, 2018 at 8:51 PM, Heiner Kallweit wrote:
>> +#define RTL8366RB_POWER_SAVE 0x21
> Typically PHY register addresses are 5 bits wide, is 0x21 correct
> and I miss something?
If it is correct I don't know, but it appears in the vendor
code:
/*Power Saving*/
#define RTL8368S_POWER_SA
similar to how we handle
interrupt controllers inside PCI bridges etc.
Cc: Antti Seppälä
Cc: Roman Yeryomin
Cc: Colin Leitner
Cc: Gabor Juhos
Cc: Florian Fainelli
Cc: devicet...@vger.kernel.org
Signed-off-by: Linus Walleij
---
ChangeLog RFCv2->v1:
- No changes, we agree on these bindi
On Mon, Jul 16, 2018 at 10:45 PM Rob Herring wrote:
> On Sat, Jul 14, 2018 at 11:45:54AM +0200, Linus Walleij wrote:
> > +The SMI "Simple Management Interface" is a two-wire protocol using
>
> At least for some other Realtek chips, the documentation I find says the
&
l the LAN ports
(lan0 .. lan3). The WAN port is yet not working.
Cc: Antti Seppälä
Cc: Roman Yeryomin
Cc: Colin Leitner
Cc: Gabor Juhos
Cc: Florian Fainelli
Signed-off-by: Linus Walleij
---
ChangeLog RFCv2->v1
- Drop the debugfs leftovers in the state container.
- Use strncpy() to get t
On Fri, Jul 20, 2018 at 6:17 PM Rob Herring wrote:
> On Tue, Jul 17, 2018 at 08:55:51AM +0200, Linus Walleij wrote:
> > It's just very different.
>
> Okay. Just wanted to make sure.
>
> Reviewed-by: Rob Herring
Thanks Rob! And thanks for asking the critical questions
eth0"
;;
dlink,dir-685)
# These are all connected to eth0 thru RTL8366RB
ucidef_set_interface_lan_wan "lan0 lan1 lan2 lan3" "wan"
;;
esac
exit 0
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ice I can look at for
inspiration?
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
a blank partition for the hddapp.tgz file and delete
it after generating the firmware image - when performing
updates manually you just want the "rd.z" file around
anyways.
Signed-off-by: Linus Walleij
---
target/linux/gemini/image/Makefile | 16 ++--
1 file changed, 10
are changed.
Signed-off-by: Linus Walleij
---
package/kernel/linux/modules/usb.mk | 11 +++
target/linux/gemini/Makefile| 2 ++
target/linux/gemini/config-4.14 | 10 +++---
target/linux/gemini/image/Makefile | 2 +-
4 files changed, 17 insertions(+), 8 deletions(-)
diff
2 "LangPack"
Inspecting the flash at 0x1f8000 and 0x1fa000 reveals each of
these starting with "RGCFG1" so we assume 0x1f8000-1fbfff is
"rgdb" of 0x4.
Signed-off-by: Linus Walleij
---
arch/arm/boot/dts/gemini-dlink-dir-685.dts | 16 ++--
The 50ms debounce is too low and give ghost bounces on some
platforms. Bump it to 100ms to make it stable.
Signed-off-by: Linus Walleij
---
arch/arm/boot/dts/gemini-dlink-dir-685.dts | 4 ++--
arch/arm/boot/dts/gemini-dlink-dns-313.dts | 2 +-
arch/arm/boot/dts/gemini-nas4220b.dts | 4
This adds the FOTG210 USB host controller to the Gemini
device trees. In the main SoC DTSI it is flagged as disabled
and then it is selectively enabled on the devices that utilize
it.
Signed-off-by: Linus Walleij
---
arch/arm/boot/dts/gemini-dlink-dir-685.dts | 8 ++
arch/arm/boot/dts
This sets the partition information on the SQ201 to be read
out from the RedBoot partition table, removes the static
partition table and sets our boot options to mount root from
/dev/mtdblock2 where the squashfs+JFFS2 resides.
Signed-off-by: Linus Walleij
---
arch/arm/boot/dts/gemini-sq201.dts
flash handling code to switch this
in and out when accessed so these lines can be used
for GPIO when flash is not accessed, and enable flash
access.
Signed-off-by: Linus Walleij
---
arch/arm/boot/dts/gemini-dlink-dir-685.dts | 35 +++---
arch/arm/boot/dts/gemini-sq
The DIR-685 needs this module compiled in for safety
(it is facing the LAN ports) and it is now using the DSA
switch architecture so swconfig is not needed.
Signed-off-by: Linus Walleij
---
target/linux/gemini/image/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/gemini
od or swconfig anymore.
A new reference design named SL93512R is available so
support it.
If the first patch is too big, the patches are also
available here:
https://dflund.se/~triad/krad/gemini/openwrt/
Linus Walleij (4):
gemini: Add v4.19 kernel patches
gemini: Switch to kernel v4.19
g
This generates images for the StorLink SL93512R reference
design which is supported in kernel v4.19.
Signed-off-by: Linus Walleij
---
target/linux/gemini/image/Makefile | 21 +
1 file changed, 21 insertions(+)
diff --git a/target/linux/gemini/image/Makefile
b/target/linux
This adds a config and augments the gemini makefile to
use kernel v4.19.
These devices work so much better with v4.19 so let's
immediately make it the default.
Signed-off-by: Linus Walleij
---
target/linux/gemini/Makefile| 2 +-
target/linux/gemini/config-4.19
This is the remainder of kernel patches for the v4.19
kernel. A whole slew of the previous patch stack is now
upstream, so this mainly contains the stuff that was
added upstream between v4.19 and v5.0-rc1, and then
the USB FOTG201 patches from Hans.
Signed-off-by: Linus Walleij
---
...pinctrl
On Mon, Jan 21, 2019 at 9:39 AM Petr Štetiar wrote:
> Linus Walleij [2019-01-19 21:28:58]:
> > If the first patch is too big, the patches are also available here:
> > https://dflund.se/~triad/krad/gemini/openwrt/
>
> is it possible to fetch it somewhere directly in Git?
enabled.
Yeah interesting, hm there is that make target for OpenWrt that cleans
up the defconfig now that I remember it, I'll try running that.
Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
mini-v4.19"
Linus Walleij (4):
gemini: Add v4.19 kernel patches
gemini: Switch to kernel v4.19
gemini: Drop switch kmod and swconfig
gemini: Add SL93512R Support
target/linux/gemini/Makefile | 2 +-
target/linux/gemini/config-4.19 | 494 +
The DIR-685 needs this module compiled in for safety
(it is facing the LAN ports) and it is now using the DSA
switch architecture so swconfig is not needed.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Resend.
---
target/linux/gemini/image/Makefile | 1 -
1 file changed, 1 delet
This adds a config and augments the gemini makefile to
use kernel v4.19.
These devices work so much better with v4.19 so let's
immediately make it the default.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Run the config through OpenWrt make kernel_oldconfig
and inspect th
This generates images for the StorLink SL93512R reference
design which is supported in kernel v4.19.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Resend.
---
target/linux/gemini/image/Makefile | 21 +
1 file changed, 21 insertions(+)
diff --git a/target/linux/gem
This is the remainder of kernel patches for the v4.19
kernel. A whole slew of the previous patch stack is now
upstream, so this mainly contains the stuff that was
added upstream between v4.19 and v5.0-rc1, and then
the USB FOTG201 patches from Hans.
Signed-off-by: Linus Walleij
---
ChangeLog v1
On Thu, Jan 24, 2019 at 7:19 PM Stijn Tintel wrote:
> On 23/01/19 19:59, Linus Walleij wrote:
> > This adds a config and augments the gemini makefile to
> > use kernel v4.19.
> >
> > These devices work so much better with v4.19 so let's
> > immediately mak
latforms (should be handled by Kconfig itself, I think upstream
needs patching).
I'm not good with USB, it's one of those things I need to learn better,
but I didn't need that config symbol at least, make V=s looks fine for
me.
Yours,
Linus Walleij
___
end-rootfs
>
> Produces similar/compatible files?
> (This would make the extra Build/sl93512r-images obsolete).
It does, I have a new patch for this.
I will not submit it again until we switch to v4.19
though, just sending the kernel patches and
config-v4.19 for next iteration.
Yours,
L
On Sat, Jan 26, 2019 at 12:29 PM Linus Walleij wrote:
> On Sat, Jan 26, 2019 at 9:29 AM Petr Štetiar wrote:
> > then I had to add missing generic symbol CONFIG_USB_ROLE_SWITCH[1] and
> > CONFIG_DRM_PANEL_SEIKO_43WVF1G[2] in order to get past kernel config step
> > while run
also available here:
https://dflund.se/~triad/krad/gemini/openwrt/
On popular request also pushed to github:
https://github.com/linusw/openwrt
Branch "gemini-v4.19"
The patches on that branch include full v4.19 enablement
(which should not be applied to OpenWrt)
Linus Walleij (2):
ge
1 - 100 of 604 matches
Mail list logo
