Hi Rafał,
On 2021-01-21 16:57, zajec5 at gmail.com (Rafał Miłecki) wrote:> On
21.05.2017 22:22, Rafał Miłecki wrote:
On 14 March 2017 at 07:37, Rafał Miłecki wrote:
My current DTS file contains following entry:
bootargs = "console=ttyS0,115200"
and it works in a following way:
Press the [f]
Hi Adrian, Matthias,
I was preparing my own patch for converting DEVICE_TYPE to a
device-specific variable.
https://github.com/mans0n/openwrt/commit/4d41dd963ae8d595ef38ea0a38ea08abdac1415d
But I stumbled on some blockers so I left it behind...
One of the blockers was the busybox hdparm.
I&#
Hi Florian,
Actually I was preparing the same patch just a moment ago, and found out
that LEDS_TRIGGER_MTD is a bool, not tristate.
On 2020-05-04 19:26, Florian Eckert wrote:
Not every target needs this LED trigger. Therefore this trigger can be
installed as kernel module.
Signed-off-by: Flo
On 2020-03-14 01:11, Adrian Schmutzler wrote:
While find_mtd_index() and find_mtd_part() are located in
/lib/functions.sh, find_mtd_chardev() has been located in
/lib/functions/system.sh.
Move the latter to the former file to keep similar functions
together.
Umm, what about mtd_get_part_size()
On 2020-03-13 23:30, Adrian Schmutzler wrote:
-Original Message-
From: mans0n [mailto:man...@gorani.run]
Sent: Freitag, 13. März 2020 14:26
To: Catrinel Catrinescu ; Adrian Schmutzler
; openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] [PATCH] .gitignore: ignore all .config
Hi Adrian,
On 2020-03-13 03:38, mail at adrianschmutzler.de (Adrian Schmutzler) wrote:
> Hi,
>
> I just wanted to source /lib/functions.sh in /lib/functions/system.sh
> (base-files package), as several functions in the latter require the
former and
> it's annoying (and untidy) to have to include
Hi,
If we are going to accept this patch, I would suggest "/.config.*"
instead of
"/.config*". That would suffice for all local usages.
Thanks.
On 2020-03-10 21:33, cc at 80211.de (Catrinel Catrinescu) wrote:
Hi Adrian
After successful testing, I always save the .config files, attaching the
Hi, sorry for my late reply.
I tried again to convert DEVICE_TYPE to device variable, and your
explanation of DEVICE_VARS was helpful. Thank you.
Currently device-type specific packages are added to DEFAULT_PACKAGES in
target.mk, so I had to move it into image.mk.
But then DEVICE_TYPE can no lo
On 20. 2. 22. 9:48 PM, m...@adrianschmutzler.de wrote:
to make a variable "per-device", you have to add it to DEVICE_VARS, e.g.
DEVICE_VARS += DEVICE_TYPE
I've tried it, but it did not work. DEVICE_VARS is used in include/image.mk but
DEVICE_TYPE is used in include/target.mk, I guess that is th
Hi,
I can't find the answers on my own, so I'm seeking help here. Any opinions
would be appreciated.
1. I found that currently four devices have set DEVICE_TYPE to nas in their
Device definition.
But when I tried defconfig, none of them actually had DEFAULT_PACKAGES.nas in
their .config.
It s
On 19. 11. 26. 1:45 AM, Adrian Schmutzler wrote:
Based on that, having dts-v1 in the dtsi is discouraged when it's in the dts
already (though not restricted by the parser ATM).
I see. So dtc does not really like the use of /dts-v1/ in DTSI files.
Thanks for letting me know. :)
__
Hi Adrian,
I already read your previous mail two weeks ago, but then I was not very
familiar with these mailing list stuff (still I am). Sorry for the late
reply.
On 19. 11. 25. 6:53 AM, Adrian Schmutzler wrote:
> The "/dts-v1/;" identifier is supposed to be put once at the beginning
> of a d
12 matches
Mail list logo
