On Thursday 04 December 2014 19:40:34 Tony Lindgren wrote:
> * Pali Rohár [141204 10:36]:
> > see last mail in thread (I CCed you):
> > "[PATCH] ARM: /proc/cpuinfo: Use DT machine name when
> > possible"
> >
> > There is already some layer for converting ATAGs to DTB and
> > it is in decompresser
* Pali Rohár [141204 10:36]:
>
> see last mail in thread (I CCed you):
> "[PATCH] ARM: /proc/cpuinfo: Use DT machine name when possible"
>
> There is already some layer for converting ATAGs to DTB and it is
> in decompresser: arch/arm/boot/compressed/atags_to_fdt.c
>
> I do not know if it can
On Friday 28 November 2014 23:24:26 Tony Lindgren wrote:
> * Pali Rohár [141128 13:43]:
> > On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> > > Are you saying there are some issues with that?
> >
> > uboot (in mode when is loaded from NOLO) has those issues:
> >
> > 1) uboot cannot re
On Wed, 03 Dec 2014 17:52:04 +0100, Pavel Machek wrote:
> On Fri 2014-11-28 12:27:19, Tony Lindgren wrote:
>> * Pali Rohár [141127 03:34]:
>> > On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
>> > >
>> > > Thinking about this probably the best long term solution is to pass
>> > > opti
On Fri 2014-11-28 12:27:19, Tony Lindgren wrote:
> * Pali Rohár [141127 03:34]:
> > On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> > >
> > > Thinking about this probably the best long term solution is
> > > to pass optional board_revision in the kernel cmdline that
> > > can be pars
On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> * Pali Rohár [141127 03:34]:
> > On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> > > Thinking about this probably the best long term solution
> > > is to pass optional board_revision in the kernel cmdline
> > > that can be par
Hi,
On Fri, Nov 28, 2014 at 11:49:00PM +0100, Pali Rohár wrote:
> On Friday 28 November 2014 23:41:35 Aaro Koskinen wrote:
> > On Fri, Nov 28, 2014 at 10:41:12PM +0100, Pali Rohár wrote:
> > > uboot (in mode when is loaded from NOLO) has those issues:
> > >
> > > 1) uboot cannot read n900 onenand
On Friday 28 November 2014 23:41:35 Aaro Koskinen wrote:
> Hi,
>
> On Fri, Nov 28, 2014 at 10:41:12PM +0100, Pali Rohár wrote:
> > uboot (in mode when is loaded from NOLO) has those issues:
> >
> > 1) uboot cannot read n900 onenand mtd (uboot onenand driver
> > not working, do not know why)
> > 2
On Friday 28 November 2014 23:26:30 Aaro Koskinen wrote:
> Hi,
>
> On Fri, Nov 28, 2014 at 10:41:12PM +0100, Pali Rohár wrote:
> > Does kernel provide some interface for telling userspace
> > applications something like bootreason (e.g power key,
> > software reset, rtc alarm, charger connected, .
On Friday 28 November 2014 23:24:26 Tony Lindgren wrote:
> * Pali Rohár [141128 13:43]:
> > On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> > > Are you saying there are some issues with that?
> >
> > uboot (in mode when is loaded from NOLO) has those issues:
> >
> > 1) uboot cannot re
Hi,
On Fri, Nov 28, 2014 at 10:41:12PM +0100, Pali Rohár wrote:
> uboot (in mode when is loaded from NOLO) has those issues:
>
> 1) uboot cannot read n900 onenand mtd (uboot onenand driver not
> working, do not know why)
> 2) missing support for battery charging (can totally discharge
> battery)
Hi,
On Fri, Nov 28, 2014 at 10:41:12PM +0100, Pali Rohár wrote:
> Does kernel provide some interface for telling userspace
> applications something like bootreason (e.g power key, software
> reset, rtc alarm, charger connected, ...)?
In N950/N9, NOLO passes this information using kernel command l
* Pali Rohár [141128 13:43]:
> On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
>
> > Are you saying there are some issues with that?
>
> uboot (in mode when is loaded from NOLO) has those issues:
>
> 1) uboot cannot read n900 onenand mtd (uboot onenand driver not
> working, do not know
On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> * Pali Rohár [141127 03:34]:
> > On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> > > Thinking about this probably the best long term solution
> > > is to pass optional board_revision in the kernel cmdline
> > > that can be par
* Pali Rohár [141127 03:34]:
> On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> >
> > Thinking about this probably the best long term solution is
> > to pass optional board_revision in the kernel cmdline that
> > can be parsed early and copied to system_rev variable.
> >
>
> Not pos
On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> * Pali Rohár [141126 15:40]:
> > With enabled CONFIG_ARM_APPENDED_DTB=y file /proc/atags is
> > missing.
>
> OK I guess it should not be needed for DT based booting.
>
If I do not enable CONFIG_ARM_APPENDED_DTB=y then kernel is
booti
> 8<
> From: Tony Lindgren
> Date: Wed, 26 Nov 2014 11:55:29 -0800
> Subject: [PATCH] ARM: OMAP2+: Fix n900 board name for legacy user space
>
> N900 legacy user space apps need the board name in
> /proc/cpuinfo to work properly for the Hardware entry.
>
> For other boards this shou
* Pali Rohár [141126 15:40]:
>
> With enabled CONFIG_ARM_APPENDED_DTB=y file /proc/atags is
> missing.
OK I guess it should not be needed for DT based booting.
> > The build_tag_list() should parse ATAG_REVISION and then
> > parse_tag_revision() should copy it to system_rev. Maybe try
> > add
On Thursday 27 November 2014 00:14:36 Tony Lindgren wrote:
> * Pali Rohár [141126 15:03]:
> > On Wednesday 26 November 2014 21:08:06 Tony Lindgren wrote:
> >
> > With your patch I'm getting:
> >
> > Hardware: Nokia RX-51 board
> >
> > So patch is good.
>
> Is that a Tested-by: then? :)
* Pali Rohár [141126 15:03]:
> On Wednesday 26 November 2014 21:08:06 Tony Lindgren wrote:
>
> With your patch I'm getting:
>
> Hardware: Nokia RX-51 board
>
> So patch is good.
Is that a Tested-by: then? :)
> > > Revision comes from bootloader (via ATAG) and it is HW
> > > revision
On Wednesday 26 November 2014 21:08:06 Tony Lindgren wrote:
> * Pali Rohár [141126 11:24]:
> > On Wednesday 26 November 2014 20:10:28 Tony Lindgren wrote:
> > > * Pali Rohár [141126 10:59]:
> > > > On Wednesday 26 November 2014 19:19:35 Tony Lindgren
wrote:
> > > > > Maybe Pali can try to restar
* Pali Rohár [141126 11:24]:
> On Wednesday 26 November 2014 20:10:28 Tony Lindgren wrote:
> > * Pali Rohár [141126 10:59]:
> > > On Wednesday 26 November 2014 19:19:35 Tony Lindgren wrote:
> > > > Maybe Pali can try to restart that discussion? To me it
> > > > seems the /proc/cpuinfo should be t
On Wednesday 26 November 2014 20:10:28 Tony Lindgren wrote:
> * Pali Rohár [141126 10:59]:
> > On Wednesday 26 November 2014 19:19:35 Tony Lindgren wrote:
> > > Maybe Pali can try to restart that discussion? To me it
> > > seems the /proc/cpuinfo should be the same as it's a user
> > > interface.
* Pali Rohár [141126 10:59]:
> On Wednesday 26 November 2014 19:19:35 Tony Lindgren wrote:
> >
> > Maybe Pali can try to restart that discussion? To me it seems
> > the /proc/cpuinfo should be the same as it's a user
> > interface. Sorry forgot the details of the previous
> > discussion..
> >
>
On Wednesday 26 November 2014 19:19:35 Tony Lindgren wrote:
> * Pavel Machek [141126 09:31]:
> > On Tue 2014-10-28 01:01:38, Aaro Koskinen wrote:
> > > Hi,
> > >
> > > On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren
wrote:
> > > > +
> > > > + if (!of_have_populated_dt())
> > > > +
* Pavel Machek [141126 09:31]:
> On Tue 2014-10-28 01:01:38, Aaro Koskinen wrote:
> > Hi,
> >
> > On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> > > +
> > > + if (!of_have_populated_dt())
> > > + pr_warn("WARNING: legacy booting deprecated, please update to
> > > boot w
On Tue 2014-10-28 01:01:38, Aaro Koskinen wrote:
> Hi,
>
> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> > +
> > + if (!of_have_populated_dt())
> > + pr_warn("WARNING: legacy booting deprecated, please update to
> > boot with .dts\n");
> > +
>
> Maybe use WARN so t
* Tony Lindgren [141101 15:00]:
> * Russell King - ARM Linux [141031 17:46]:
>
> > However, these are minor compared to the dreadful poweroff behaviour.
> > Still going to have to disable DT booting for the LDP because of that.
>
> Sure, I'll let you know as soon as I have something available
* Russell King - ARM Linux [141031 17:46]:
> On Fri, Oct 31, 2014 at 04:37:23PM -0700, Tony Lindgren wrote:
> >
> > Like I posted in this thread, I'm not seeing same errors as you are
> > with your config modified for DT:
> >
> > http://muru.com/for-rmk/dmesg-ldp-dt-v3.18-rc2
>
> Gah, the build
On Fri, Oct 31, 2014 at 04:37:23PM -0700, Tony Lindgren wrote:
> * Russell King - ARM Linux [141031 15:35]:
> > On Fri, Oct 31, 2014 at 02:13:26PM -0700, Tony Lindgren wrote:
> > > * Russell King - ARM Linux [141031 12:32]:
> > >
> > > > WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c
* Russell King - ARM Linux [141031 15:35]:
> On Fri, Oct 31, 2014 at 02:13:26PM -0700, Tony Lindgren wrote:
> > * Russell King - ARM Linux [141031 12:32]:
> >
> > > WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2538
> > > _init+0xc8/0x170()
> > > omap_hwmod: ssi: doesn't have mpu r
On Fri, Oct 31, 2014 at 02:13:26PM -0700, Tony Lindgren wrote:
> * Russell King - ARM Linux [141031 12:32]:
> >
> > Last night I tried enabling DT booting on the LDP. This resulted in
> > quite a horrid mess, so I don't think you're there still.
>
> Thanks for trying. Other than the mystery bat
* Tony Lindgren [141031 14:16]:
> * Russell King - ARM Linux [141031 12:32]:
> >
> > Last night I tried enabling DT booting on the LDP. This resulted in
> > quite a horrid mess, so I don't think you're there still.
>
> Thanks for trying. Other than the mystery battery issue, the others
> shoul
* Russell King - ARM Linux [141031 12:32]:
>
> Last night I tried enabling DT booting on the LDP. This resulted in
> quite a horrid mess, so I don't think you're there still.
Thanks for trying. Other than the mystery battery issue, the others
should pretty much go away with just .config changes
On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> We're moving omaps to use device tree based booting and already have
> omap2, omap4, omap5, am335x and am437x booting in device tree only
> mode.
>
> Only omap3 still has legacy booting still around and we really want
> to make that
On 10/29/2014 05:31 PM, Aaro Koskinen wrote:
Also, you cannot expect all kernel users to know what you have been
talking about. E.g. OMAP DMA API deprecation may have been discussed
before, but I only learned it after the WARN appeared in the kernel tree.
So you should start counting from that.
Hello Tony,
On Thu, Oct 30, 2014 at 12:11 AM, Aaro Koskinen wrote:
> On Wed, Oct 29, 2014 at 12:39:16PM -0700, Tony Lindgren wrote:
>> From: Tony Lindgren
>> Date: Mon, 27 Oct 2014 13:05:54 -0700
>> Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
>
On Wed, Oct 29, 2014 at 12:39:16PM -0700, Tony Lindgren wrote:
> From: Tony Lindgren
> Date: Mon, 27 Oct 2014 13:05:54 -0700
> Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
>
> We're moving omaps to use device tree based booting and already have
&
Hi,
On Wed, Oct 29, 2014 at 12:39:16PM -0700, Tony Lindgren wrote:
> 8< ---
> From: Tony Lindgren
> Date: Mon, 27 Oct 2014 13:05:54 -0700
> Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
>
> We're moving omaps to use dev
On Wed, Oct 29, 2014 at 04:45:41PM -0500, Nishanth Menon wrote:
> On 12:39-20141029, Tony Lindgren wrote:
> > OK, you want me to guess? A hundred million days, or maybe ten more
> > minutes, somewhere in there, I just can't say, don't know.
>
> How about ~1 year? We have been talking about dt only
* Nishanth Menon [141029 14:47]:
> On 12:39-20141029, Tony Lindgren wrote:
> > * Sebastian Reichel [141029 12:01]:
> > > Hi,
> > >
> > > On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> > > > On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > > > > * Aaro Koskinen [141027 16:03]:
On 12:39-20141029, Tony Lindgren wrote:
> * Sebastian Reichel [141029 12:01]:
> > Hi,
> >
> > On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> > > On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > > > * Aaro Koskinen [141027 16:03]:
> > > >> Hi,
> > > >>
> > > >> On Mon, Oct 27,
e have objections to that.
> Apart from that I wonder if we should drop support on a
> board-by-board basis and then drop omap3 support completly once all
> boards have been dropped.
Yes. I'll post few patches from my old board removal branch at
omap-for-v3.14/omap3-board-removal shor
Hi,
On Wed, Oct 29, 2014 at 08:43:03AM -0500, Nishanth Menon wrote:
> On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> > * Aaro Koskinen [141027 16:03]:
> >> Hi,
> >>
> >> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> >>> +
> >>> + if (!of_have_populated_dt())
> >>> + pr_
On 10/28/2014 05:12 PM, Tony Lindgren wrote:
> * Aaro Koskinen [141027 16:03]:
>> Hi,
>>
>> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
>>> +
>>> + if (!of_have_populated_dt())
>>> + pr_warn("WARNING: legacy booting deprecated, please update to
>>> boot with .dts\n"
* Aaro Koskinen [141027 16:03]:
> Hi,
>
> On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> > +
> > + if (!of_have_populated_dt())
> > + pr_warn("WARNING: legacy booting deprecated, please update to
> > boot with .dts\n");
> > +
>
> Maybe use WARN so that the warning
Hi,
On Mon, Oct 27, 2014 at 01:00:09PM -0700, Tony Lindgren wrote:
> +
> + if (!of_have_populated_dt())
> + pr_warn("WARNING: legacy booting deprecated, please update to
> boot with .dts\n");
> +
Maybe use WARN so that the warning is more verbose and kernel gets tainted?
A.
--
T
We're moving omaps to use device tree based booting and already have
omap2, omap4, omap5, am335x and am437x booting in device tree only
mode.
Only omap3 still has legacy booting still around and we really want
to make that device tree only. So let's add a warning about deprecated
legacy booting so
48 matches
Mail list logo
