Re: [PATCH dt-schema] schemas: chosen: Add OpenWrt LEDs properties for system states
Hi Krzysztof,
On Tue, Jan 9, 2024 at 8:10 PM Krzysztof Kozlowski
wrote:
> On 09/01/2024 17:38, Rafał Miłecki wrote:
> > On 9.01.2024 10:02, Krzysztof Kozlowski wrote:
> >> On 09/01/2024 09:23, Rafał Miłecki wrote:
> >>> From: Rafał Miłecki
> >>>
> >>> OpenWrt project provides downstream support for thousands of embedded
> >>> home network devices. Its custom requirement for DT is to provide info
> >>> about LEDs roles. Currently it does it by using custom non-documented
> >>> aliases. While formally valid (aliases.yaml doesn't limit names or
> >>> purposes of aliases) it's quite a loose solution.
> >>>
> >>> Document 4 precise "chosen" biding properties with clearly documented
> >>> OpenWrt usage. This will allow upstreaming tons of DTS files that noone
> >>
> >> typo: none
> >
> > typo: no one ;)
> >
> >>> cared about so far as those would need to be patched downstream anyway.
> >>
> >> From all this description I understand why you want to add it, but I
> >> don't understand what are you exactly adding and how it is being used by
> >> the users/OS.
> >
> > In OpenWrt we have user space script that reads LED full path:
> > cat /proc/device-tree/aliases/led-
> >
> > And then sets LED to state matching current boot stage:
> > echo 1 > /sys/class/leds//brightness
>
> OK, it's nowhere close to a hardware property. You now instruct OS what
> to do. It's software or software policy.
> >> Anyway, we have existing properties for this - LED functions. Just
> >> choose LED with given function (from sysfs) and you are done. If
> >> function is missing in the header: feel free to go, least for me.
> >
> > In "Describing LEDs roles in device tree?" e-mail I wrote:
> >
> > "
> > Please note that "function" on its own is not sufficient as multiple
> > LEDs my share the same function name but its meaning may vary depending
> > on color.
> > "
> >
> > Let me elaborate here.
> >
> > Values of "function" property match LEDs descriptions (usually it's a
> > physical label). That is OK and makes sense but doesn't allow OpenWrt to
> > automatically pick proper LED to use during given boot stage.
> >
> > Some devices may have multiple color of a the same LED function. OpenWrt
> > developer needs to choose which color to use for failsafe more and which
> > boot fully booted state (and others too).
> >
> > Devices also differ in available LEDs by their functions. Some may have
> > LED_FUNCTION_POWER that OpenWrt needs to use. Some may have
> > LED_FUNCTION_STATUS. Or both. There are some more (less common)
> > functions like LED_FUNCTION_ACTIVITY.
> >
> > We failed at OpenWrt to develop a single generic script to rule all
> > devices and all their LEDs combinations. We ended up with developers
> > *choosing* what LED to use for a given system state.
>
> So this all is because you want to write easier OS. That's abuse of
> Devicetree. You can define which LEDs have different meaning, e.g.
> physical label or icon attached to them. That's a hardware property.
>
> You can also define how pieces of hardware are wired together and create
> entire system, e.g. connect one LED to disk activity.
>
> However what you are proposing here is to dynamically configure one,
> given OS. I don't think it is suitable.
>
> The problem of OS to nicely figure out which LED to blink when, is not a
> problem of Devicetree. It is a problem of OS and its configuration.
I'd say it's a grey area...
What if the colors are printed on the case, next to the LED?
Like these multi-color LEDs indicating port speed on network switches?
Then it suddenly becomes hardware description, just like
"aliases/serial2 = &...;" referring to serial port 2.
Next, what if the colors are not printed on the case, but documented
in the product's manual?
What if there is no paper product manual, but just the OpenWRT online
documentation?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ARM board lockups/hangs triggered by locks and mutexes
Hi Rafal,
On Mon, Aug 7, 2023 at 1:11 PM Rafał Miłecki wrote:
> On 4.08.2023 13:07, Rafał Miłecki wrote:
> > I triple checked that. Dropping a single unused function breaks kernel /
> > device stability on BCM53573!
> >
> > AFAIK the only thing below diff actually affects is location of symbols
> > (I actually verified that by comparing System.map before and after -
> > over 22'000 of relocated symbols).
> >
> > Can some unfortunate location of symbols cause those hangs/lockups?
>
> I performed another experiment. First I dropped mtd_check_of_node() to
> bring kernel back to the stable state.
>
> Then I started adding useless code to the mtdchar_unlocked_ioctl(). I
> ended up adding just enough to make sure all post-mtd symbols in
> System.map got the same offset as in case of backporting
> mtd_check_of_node().
>
> I started experiencing lockups/hangs again.
>
> I repeated the same test with adding dumb code to the brcm_nvram_probe()
> and verifying symbols offsets following brcm_nvram_probe one.
>
> I believe this confirms that this problem is about offset or alignment
> of some specific symbol(s). The remaining question is what symbols and
> how to fix or workaround that.
I had similar experiences on other ARM platforms many years ago:
bisection lead to something completely bogus, and it turned out
adding a single line of innocent code made the system lock-up or crash
unexpectedly. It was definitely related to alignment, as adding the
right extra amount of innocent code would fix the problem. Until some
later change changing alignment again...
I never found the real cause, but the problems went away over time.
I am not sure I did enable all required errata config options, so I
may have missed some...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ARM BCM53573 SoC hangs/lockups caused by locks/clock/random changes
Hi Rafał,
On Mon, Sep 4, 2023 at 10:35 AM Rafał Miłecki wrote:
> 2. Clock (arm,armv7-timer)
>
> While comparing main clock in Broadcom's SDK with upstream one I noticed
> a tiny difference: mask value. I don't know it it makes any sense but
> switching from CLOCKSOURCE_MASK(56) to CLOCKSOURCE_MASK(64) in
> arm_arch_timer.c (to match SDK) increases average uptime (time before a
> hang/lockup happens) from 4 minutes to 36 minutes.
That code path is used only for type != ARCH_TIMER_TYPE_CP15,
but your kernel log
arch_timer: cp15 timer(s) running at 0.03MHz (virt).
suggest that type == ARCH_TIMER_TYPE_CP15?!?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] RFC: ARM: dts: Proposed Goramo MultiLink device tree
Hi Linus,
On Thu, Jul 29, 2021 at 1:54 AM Linus Walleij wrote:
> This is an example of how I think the Goramo MultiLink device can
> be supported in the device tree.
>
> It requires writing a new 74hc4094 GPIO driver and moving a bunch
> of the boardfile code into the HSS driver as it is anyways the only
> user of this facility. If there are other boards supporting HSS they
> can be added too.
Can't the existing drivers/gpio/gpio-74x164.c be used?
See also Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/3] ARM: dts: Att Vitesse G5e switch to the Gemini SQ201
Hi Linus,
On Wed, Jul 4, 2018 at 9:21 PM Linus Walleij wrote:
> This adds the Vitesse G5e ethernet switch to the Square
> One Itian SQ201 router device tree.
>
> Signed-off-by: Linus Walleij
Thanks for your patch!
> --- a/arch/arm/boot/dts/gemini-sq201.dts
> +++ b/arch/arm/boot/dts/gemini-sq201.dts
> @@ -20,7 +20,7 @@
> };
>
> chosen {
> - bootargs = "console=ttyS0,115200n8";
> + bootargs = "console=ttyS0,115200n8 root=/dev/sda1 rw
> rootwait";
> stdout-path = &uart0;
> };
The above hunk looks unrelated.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [CFP] FOSDEM 2015 Embedded Devroom
Devroom date: Saturday January 31st and February 1st 2015 in Brussels,
Belgium
CFP deadline: Monday December 1st 2014
Final notification two weeks later, December 15th 2014
CFP Introduction
--
Embedded software is transforming the world, and FOSS embedded software is
leading the way. From automotive to the Internet of Things, small devices,
embedded systems, industrial process control and automatons are beginning
their inevitable rise to the singularity. Join in! Or be assimilated. ;)
NB: This year FOSDEM plans to record all presentations, no exceptions.
Please only propose a talk that you're really able and willing to share.
Topics Sought
--
The embedded devroom seeks topics related to automotive, mobile,
autonomous, and generally small systems. Related areas are of course of
interest as well and our definition of "embedded" is elastic. Are you
controlling and launching rockets, made your own set-top box, built some
heating control for your house, hacked your mobile phone or just built a
small gadget using FOSS software then you might have exactly what we're
looking for. This year the automotive devroom has been merged into the
embedded devroom so automotive projects are for sure on topic here too.
CFP Schedule And Submission Details
Please submit proposals no later than the first of December.
Please use the following URL to submit your talk to FOSDEM 2015:
https://penta.fosdem.org/submission/FOSDEM15
and follow the following rules:
* Select as the Track "embedded devroom".
* Include a title. (Note that "Subtitle" entry doesn't appear on
all conference documents, so make sure "Title" can stand on its own without
"Subtitle" present.) Also try to make it catchy and descriptive of what you
will talk about. For example "Launching rockets with an Arduino" and not
"Programming a microcontroller for aerodynamic control"
* Include an Abstract of about 500 characters and a full description of
any length you wish, but in both fields, please be concise, but clear and
descriptive.
* Indicate whether you seek a 25 or 45 minute slot.
* Use the "Links" sub-area to your past work in the field you'd like to
share.
* Affirmative confirmation that you agree to CC-By-SA-4.0 or Cc-By-4.0
licensing of your talk, in the "Submission Notes" field. Add a statement
such as this: "Should my presentation be scheduled for FOSDEM 2015, I
hereby agree to license all recordings, slides and any other materials
presented under the Creative Commons Attribution Share-Alike 4.0
International license. Sincerely, s/YOUR_NAME/"
* Also in the notes field, note your affirmative confirmation of
availability to speak on Saturday 31 January or 1 February 2015 in
Brussels. Also mention if you plan to do a demo and if you have special
requirements.
* Make sure you give a valid email so we can contact you easily in case
we have more questions or want to make sure you received the confirmation.
Should you have any questions we can send more information as needed.
Thank you very much and we look forward to reviewing your proposals!
-- Philippe and Jeremiah along with the other members of
the FOSDEM embedded devroom team.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [CFP] FOSDEM 2015 Embedded Devroom
Devroom date: Saturday January 31st and February 1st 2015 in Brussels,
Belgium
CFP deadline: Monday December 1st 2014
Final notification two weeks later, December 15th 2014
CFP Introduction
--
Embedded software is transforming the world, and FOSS embedded software is
leading the way. From automotive to the Internet of Things, small devices,
embedded systems, industrial process control and automatons are beginning
their inevitable rise to the singularity. Join in! Or be assimilated. ;)
NB: This year FOSDEM plans to record all presentations, no exceptions.
Please only propose a talk that you're really able and willing to share.
Topics Sought
--
The embedded devroom seeks topics related to automotive, mobile,
autonomous, and generally small systems. Related areas are of course of
interest as well and our definition of "embedded" is elastic. Are you
controlling and launching rockets, made your own set-top box, built some
heating control for your house, hacked your mobile phone or just built a
small gadget using FOSS software then you might have exactly what we're
looking for. This year the automotive devroom has been merged into the
embedded devroom so automotive projects are for sure on topic here too.
CFP Schedule And Submission Details
Please submit proposals no later than the first of December.
Please use the following URL to submit your talk to FOSDEM 2015:
https://penta.fosdem.org/submission/FOSDEM15
and follow the following rules:
* Select as the Track "embedded devroom".
* Include a title. (Note that "Subtitle" entry doesn't appear on
all conference documents, so make sure "Title" can stand on its own without
"Subtitle" present.) Also try to make it catchy and descriptive of what you
will talk about. For example "Launching rockets with an Arduino" and not
"Programming a microcontroller for aerodynamic control"
* Include an Abstract of about 500 characters and a full description of
any length you wish, but in both fields, please be concise, but clear and
descriptive.
* Indicate whether you seek a 25 or 45 minute slot.
* Use the "Links" sub-area to your past work in the field you'd like to
share.
* Affirmative confirmation that you agree to CC-By-SA-4.0 or Cc-By-4.0
licensing of your talk, in the "Submission Notes" field. Add a statement
such as this: "Should my presentation be scheduled for FOSDEM 2015, I
hereby agree to license all recordings, slides and any other materials
presented under the Creative Commons Attribution Share-Alike 4.0
International license. Sincerely, s/YOUR_NAME/"
* Also in the notes field, note your affirmative confirmation of
availability to speak on Saturday 31 January or 1 February 2015 in
Brussels. Also mention if you plan to do a demo and if you have special
requirements.
* Make sure you give a valid email so we can contact you easily in case
we have more questions or want to make sure you received the confirmation.
Should you have any questions we can send more information as needed.
Thank you very much and we look forward to reviewing your proposals!
-- Philippe and Jeremiah along with the other members of
the FOSDEM embedded devroom team.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] git.infradead.org offline? mirror for mtd-utils-1.4.5?
On Fri, Oct 24, 2014 at 9:48 AM, Claudio Thomas wrote:
> fatal: unable to connect to git.infradead.org:
> git.infradead.org: Name or service not known
It seems to be up again.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kernel module runtime configuration
Hi Brent,
On Fri, Aug 15, 2014 at 12:45 AM, Brent Thomson wrote:
> Hey all. I'm working on my first Linux kernel module. It's an
> adaptation of an hd44780-over-GPIO driver. You can see it here:
>
> https://github.com/brnt/openwrt-hd44780
>
> The driver is working fine, but I'd like to allow the user to
> configure which GPIOs are used by the driver. Rather than hard-coding
> the values in the C file (as they're currently done) I'd prefer to
> read values from a config file (or the equivalent).
The modern way to do this is to add a hd44780-gpio device node to the
device tree, cfr. spi-over-gpio:
Documentation/devicetree/bindings/spi/spi-gpio.txt
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Quick hack for kernel entropy problem on MIPS
On Thu, Oct 17, 2013 at 6:32 PM, Weedy wrote:
> On Thu, Oct 17, 2013 at 11:40 AM, chrono wrote:
>> Ahoi everyone,
>>
>> it was requested on IRC that I send my solution to the entropy problem with
>> the current
>> kernel (e.g. having 0 available entropy):
>>
>> root@OpenWrt:/# cat /proc/sys/kernel/random/entropy_avail
>> 0
> Uhh ok?
> root@OpenWrt:~# cat /proc/sys/kernel/random/entropy_avail
> 1189
What's your uptime? Entropy is added to the pool e.g. based on network
activity. The issue is that the pool is empty right after boot up.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Let's fix the OpenWrt patch acceptance problem!
On Sat, Jan 28, 2012 at 06:43, Philip Prindeville
wrote:
> Recently I submitted a patch for 3.2 and it was rejected because it didn't
> include versions for early kernel releases (2.6.39, 3.0, and 3.1). Another
> patch I suggested that was for 2.6.39 which I had extensively tested was
> rejected because the person I had asked "was tired of maintaining so many
> versions" and "wanted to kill off the older versions".
An easy way to work around the former rejection is to submit the patch
upstream ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Let's fix the OpenWrt patch acceptance problem!
On Tue, Jan 24, 2012 at 16:16, Felix Fietkau wrote:
> Probably not going to happen for the main repo. Some developers like to
> stay with SVN. Right now I don't see a point in pushing for a complete
> switch to git, since the svn<->git integration is working just fine.
While git-svn is bidirectional, there are limitations when working with other
people using git:
- After pulling from another git repository, you cannot just dcommit the
result to the svn repository. You must rebase or cherry-pick it on top of
your branch you use to sync with svn.
- You loose the original authorship, as dcommit will commit it to svn as
your own.
Disclaimer: it's been a few months I used git-svn, so things may have changed
in the mean time. Welcome to the road to heaven^H^H^H^H^H^Hgit ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Fosdem embedded and mobile devroom call for papers
Fosdem will be held the 4th and 5th of February 2012 in Brussels,
Belgium. As usual and for the 9th time there will be an embedded and
mobile room.
For this years program we are looking for people who would like to do
a presentation about their or their community's projects in this area.
These projects must be Free Software or Open Source.
For example involvement and experiences with projects like Arduino,
Meego/Tizen, Mer, Beagleboard, Openembedded, Android, OpenWrt, Yocto, Linaro...
Also we are interested in short tutorials, project overviews,
achievements, ports to new hardware and hardware hacking, real life deployments,
...all are welcome and all submissions will be reviewed by our panel.
Submissions require a small abstract and short speaker presentation
and should be submitted to fosdem.embed...@gmail.com.before the 15th of
january of 2012
The panel consists of:
Philippe De Swert
Peter De Schrijver
Klaas Van Gend
Dave Neary
Michael Opdenacker
Geert Uytterhoeven
Looking forward to see you all at Fosdem (http://www.fosdem.org/)!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] replace CONFIG_PREEMPT_NONE with CONFIG_PREEMPT
On Fri, Sep 2, 2011 at 12:39, Luka Perkov wrote:
> On Fri, Sep 02, 2011 at 10:46:37AM +0200, Florian Fainelli wrote:
>> On Friday 02 September 2011 00:55:54 Luka Perkov wrote:
>> > Also in linux-2.6.39.4/kernel/Kconfig.preempt you will see for
>> > CONFIG_PREEMPT:
>> >
>> > Select this if you are building a kernel for a desktop or
>> > embedded system with latency requirements in the milliseconds
>> > range
>
> Please look at the kernel config file above. You will see that
> CONFIG_PREEMPT should be used on embedded systems...
... with latency requirements in the milliseconds range.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Optimize for speed, not for size
On Mon, Jan 17, 2011 at 08:32, Bastian Bittorf wrote:
>> The -O3 optimization adds a good bit of size that means more page
>> faults and cache misses, which translates to slower real-world
>> performance.
>
> this is theory as must be checked.
> our routers are so powerful (16mb RAM or more, these
> where workstations some years ago), so we
> have enough space and maybe can achieve a little
> bit more speed...
Do they also have as much (L2) cache as your workstations some years ago?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] update and optimize git package
On Wed, Nov 17, 2010 at 13:09, Bastian Pranzas wrote:
> - create symlinks instead of hardlinks when installing (hardlinks get
> lost when copying)
Isn't that a bug in the copying code?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] patch submission guidelines
On Mon, Jun 1, 2009 at 19:38, Bud wrote:
> I just read on
> https://dev.openwrt.org/wiki/SubmittingPatches
>
> that patches should be delivered as follows
>
> Send a mail to openwrt-devel lists.openwrt.org with the following
> contents:
> 1. [PATCH] in the Subject, followed by:
> 2. (optional) a longer description of your patch in the message body
> 3. Signed-off-by: Your name
> 4. Your actual patch, inline, not word wrapped or whitespace mangled.
>
> Why is it so? Is there an automated process integrating them?
The reasoning behind this is actually mentionted 2 lines below the
lines you're quoting:
to mimic the Linux kernel patch submission process.
> What about additions (new files) that are not version controlled yet?
Diff handles them fine (difference against empty/nonexistent file).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] adm5120 linux-2.6.28 patches
On Sun, 25 Jan 2009, Alexandros C. Couloumbis wrote:
> you may find working patches for this platform here:
> http://wifi.ozo.com/airo/openwrt/source/adm5120/kernel/2.6.28/
Thanks! But it seems these patches do not include the _new_ files, only
modifications to existing files?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] added GPIO driver for CS5535/CS5536 companion chip
On Wed, 7 Jan 2009, Andy Boyett wrote:
> Make it x86 specific and I'll commit it. No sense in building modules on
> platforms that will never use them.
JFYI, AMD's CS5536 companion chip is also used on Lemote's Fuloong, which is
mips: http://www.linuxdevices.com/news/NS2928309621.html.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] New Patchwork beta (fwd)
Given the recent discussions about keeping track of patches, perhaps Patchwork could be useful for OpenWRT, too? (http://ozlabs.org/~jk/projects/patchwork/) With kind regards, Geert Uytterhoeven Software Architect Sony Techsoft Centre Europe The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium Phone:+32 (0)2 700 8453 Fax: +32 (0)2 700 8622 E-mail: [EMAIL PROTECTED] Internet: http://www.sony-europe.com/ A division of Sony Europe (Belgium) N.V. VAT BE 0413.825.160 · RPR Brussels Fortis · BIC GEBABEBB · IBAN BE41293037680010 -- Forwarded message -- Date: Thu, 21 Aug 2008 18:22:26 +0800 From: Jeremy Kerr <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: New Patchwork beta Hi all, I've just put up a new beta of patchwork: http://patchwork2.ozlabs.org/ I intend to replace the existing patchwork with the new code, but would like to get it tested first. There aren't many patches in the system at the moment, but it'll receive patches from the relevant lists. I'll also import a set of existing mails tomorrow, to give some sample data to test with. One important note - after beta testing, I'm planning to clear the test database and start from scratch. So, don't go spending too much time updating patches! However, have a play with the new site, let me know what breaks, and any suggestions for changing, and we can work towards a full replacement for the current site. Some differences from the old patchwork: * Patches can now be 'delegated' to other maintainers - this means that maintainers can offload subsystem-specific patches to other maintainers. * Anyone can create an account, and work with bundles, and manage their own patches. * Pagination. No more 10MB patch lists! * Bundles can be made public, allow users to share patchsets * Better filtering interface Project Maintainers: Create an account, then send me your username, and I'll add maintainer privileges to your account. Again, don't go too crazy with the maintaining work, as it'll all be cleared out once we replace patchwork.ozlabs.org Also: bazaar-ng, linux-mtd and linux-embedded folks: are you still using patchwork? Existing patches: After talking to the powerpc maintainers, we've decided that we're going to start with a clean slate, and not import patches from the existing patchwork database. If you'd prefer to keep current patches for your project, let me know. This will be a bit of work, but I'm sure we can work something out. Happy patchworking, Jeremy ___ Linuxppc-dev mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-dev___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] trying to get a usb storage mounted on root
On Sat, 12 Jul 2008, RHS Linux User wrote:
> If I understand your point about the 3rd option?
>
> 1. The driver(s) could either be in the kernel,
>
> 2. In the greater kernel image (flash chip) as drivers loaded after
> kernel boot.
>
> 3. On some removeable device (USB or whatever).
>
> If the drivers are capable of being loaded by the kernel, then they
> could be either in 2 or 3.
>
> Except that the drivers necessary to "mount" or make available the
> device of #3 (USB or whatever), "must" reside in 2. These drivers could be
> either linked statically to the particular kernel image or not.
>
>
> There is one additional point that is probably relevant.
>
> The boot kernel could be replaced by a kernel and filesystem provided
> by the USB or whatever device.
>
> IMHO getting this sort of KERNEL-PIVOT operation really working would
> be the best of all. The boot kernel would only be used for boot and debug
> and a "real" kernel could run "real" applications on the USB. The boot
> kernel could even become a "task" running under the new kernel.
If your platform supports kexec, you can boot a new kernel from the boot
kernel.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to submit patches to OpenWRT
On Tue, 24 Jun 2008, RB wrote:
> > How would it look if OpenWrt tried to write into each of the package
> > make files who's maintaining them - something like this:
>
>
> I think that could work. AFAICT it still doesn't cover updates to
> trunk and its packages, but it's a start in the direction of helping
> focus updates for at least part of the tree. I've not investigated
> how make handles non-ASCII characters, but it'll be at least something
> to consider when setting non-Anglo names.
I gave it a quick try (both `=' and `:=' assignment), and make 3.81 on
Debian had no problems with the few UTF-8 characters I tried (á and š).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] GCC4.3 patch (wip)
On Fri, 13 Jun 2008, Luigi 'Comio' Mantellini wrote:
> I'm still working to port OpenWRT on my architecture (m68k/coldfire). I
> diff --git a/target/linux/generic_m68k/config-default
> b/target/linux/generic_m68k/config-default
> new file mode 100644
> index 000..6f8acb5
> --- /dev/null
> +++ b/target/linux/generic_m68k/config-default
> @@ -0,0 +1,616 @@
> +#
> +# Automatically generated make config: don't edit
> +# Linux kernel version: 2.6.25
> +# Mon May 12 19:37:01 2008
> +#
> +CONFIG_MIPS=y
That looks a bit strange for an m68k config...
> diff --git a/target/linux/generic_m68k/image/lzma-loader/src/Makefile
> b/target/linux/generic_m68k/image/lzma-loader/src/Makefile
> new file mode 100644
> index 000..910172c
> --- /dev/null
> +++ b/target/linux/generic_m68k/image/lzma-loader/src/Makefile
> @@ -0,0 +1,68 @@
> +#
> +# Copyright (C) 2006 OpenWrt.org
> +#
> +# This is free software, licensed under the GNU General Public License v2.
> +# See /LICENSE for more information.
> +#
> +RAMSTART = 0x8000
> +RAMSIZE = 0x0010 # 1MB
> +LOADADDR = 0x8040# RAM start + 4M
> +KERNEL_ENTRY = 0x80001000
> +IMAGE_COPY:=0
> +
> +CROSS_COMPILE = mips-linux-
Another one...
> diff --git a/target/linux/generic_m68k/image/lzma-loader/src/decompress.c
> b/target/linux/generic_m68k/image/lzma-loader/src/decompress.c
> new file mode 100644
> index 000..45ac509
> --- /dev/null
> +++ b/target/linux/generic_m68k/image/lzma-loader/src/decompress.c
> +#define cache_unroll(base,op)\
> + __asm__ __volatile__( \
> + ".set noreorder;\n" \
> + ".set mips3;\n" \
> + "cache %1, (%0);\n" \
> + ".set mips0;\n" \
> + ".set reorder\n"\
> + : \
> + : "r" (base), \
> + "i" (op));
Erhm...
And there are many more...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] OpenWRT for Linux/m68k?
Given my positive experiences with OpenWRT on adm5120 (RouterBoard 150) and
PS3, I recently tried getting OpenWRT to work on m68k `hardware' (actually a
virtual Atari using ARAnyM, as that's the easiest for development :-).
I just had to add
target/linux/atari/Makefile
target/linux/atari/config-2.6.25
target/linux/atari/image/Makefile
target/linux/atari/patches/*
toolchain/uClibc/config/m68k
and use an appropriate .config, and the resulting kernel with built-in
ramdisk booted fine under ARAnyM!
My first attempt is at
http://users.telenet.be/geertu/Download/openwrt-atari.tar.bz2
Just extract it to the OpenWRT trunk root and run `make oldconfig; make'.
Perhaps this can become a valid alternative to Debian?
I still have a few questions, though:
1. target/linux/atari/patches/* is just all patch files from my quilt patch
series for 2.6.25, with each patch file name prefixed by a number to
ensure the correct order.
Can the OpenWRT build system handle plain quilt series, too? I
have to admit I didn't try.
Can the OpenWRT build system handle getting the quilt series from
http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-patches-2.6.25/?
2. Originally I had libpcap enabled in my .config. But that failed
with:
| checking Linux kernel version... unknown
| configure: error: cannot determine linux version when cross-compiling
| make[3]: *** [openwrt/build_dir/m68k/libpcap-0.9.4/.configured] Error 1
However, it worked fine for my earlier adm5120 build?
Thanks for your answers/comments!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
