>
> Other boards (don't have a specific example here, perhaps Andrew can
> provide one) need to store the reboot reason on disk.
For this case, I'm trying to get the alternate boot logic to work on PC
compatible devices. I have a patch against SYSLINUX which reads this area and
selects an alter
On Sat, Jul 7, 2012 at 4:05 PM, Greg KH wrote:
> On Sat, Jul 07, 2012 at 03:39:09PM -0700, Colin Cross wrote:
>> On many (most?) ARM SoCs, the reboot flag is not stored on disk, or
>> anywhere else userspace can access. It is stored in a power
>> management controller scratch register that surviv
On Sat, Jul 07, 2012 at 03:39:09PM -0700, Colin Cross wrote:
> On many (most?) ARM SoCs, the reboot flag is not stored on disk, or
> anywhere else userspace can access. It is stored in a power
> management controller scratch register that survives resets, or a
> register in an external I2C PMIC, o
On Sun, Jul 1, 2012 at 5:10 PM, NeilBrown wrote:
> On Fri, 29 Jun 2012 21:37:36 -0700 Colin Cross wrote:
>
>> What's the point of the existing syscall option if it doesn't work on
>> all platforms, or at least all platforms that want to support it? It
>> doesn't make sense to me to use REBOOT2 o
On Fri, 29 Jun 2012 21:37:36 -0700 Colin Cross wrote:
> What's the point of the existing syscall option if it doesn't work on
> all platforms, or at least all platforms that want to support it? It
> doesn't make sense to me to use REBOOT2 on some SoCs because they
> happen to use something that
On Fri, Jun 29, 2012 at 9:19 PM, Greg KH wrote:
> On Fri, Jun 29, 2012 at 08:43:34PM -0700, Colin Cross wrote:
>> On Fri, Jun 29, 2012 at 8:23 PM, Greg KH wrote:
>> > On Fri, Jun 29, 2012 at 12:36:30PM -0700, Andrew Boie wrote:
>> >> Android userspace tells the kernel that it wants to boot into r
On Fri, Jun 29, 2012 at 08:43:34PM -0700, Colin Cross wrote:
> On Fri, Jun 29, 2012 at 8:23 PM, Greg KH wrote:
> > On Fri, Jun 29, 2012 at 12:36:30PM -0700, Andrew Boie wrote:
> >> Android userspace tells the kernel that it wants to boot into recovery
> >> or some other non-default OS environment
On Fri, Jun 29, 2012 at 8:23 PM, Greg KH wrote:
> On Fri, Jun 29, 2012 at 12:36:30PM -0700, Andrew Boie wrote:
>> Android userspace tells the kernel that it wants to boot into recovery
>> or some other non-default OS environment by passing a string argument
>> to reboot(). It is left to the OEM to
On Fri, Jun 29, 2012 at 12:36:30PM -0700, Andrew Boie wrote:
> Android userspace tells the kernel that it wants to boot into recovery
> or some other non-default OS environment by passing a string argument
> to reboot(). It is left to the OEM to hook this up to their specific
> bootloader.
How doe
On Fri, Jun 29, 2012 at 09:56:36PM +, Boie, Andrew P wrote:
> > From: NeilBrown [mailto:ne...@suse.de]
> > Sent: Friday, June 29, 2012 2:25 PM
> >
> > On Fri, 29 Jun 2012 12:36:30 -0700 Andrew Boie
> > wrote:
> >
> > > Android userspace tells the kernel that it wants to boot into recovery
>
> From: NeilBrown [mailto:ne...@suse.de]
> Sent: Friday, June 29, 2012 2:25 PM
>
> On Fri, 29 Jun 2012 12:36:30 -0700 Andrew Boie
> wrote:
>
> > Android userspace tells the kernel that it wants to boot into recovery
> > or some other non-default OS environment by passing a string argument
> > to
On Fri, 29 Jun 2012 12:36:30 -0700 Andrew Boie
wrote:
> Android userspace tells the kernel that it wants to boot into recovery
> or some other non-default OS environment by passing a string argument
> to reboot(). It is left to the OEM to hook this up to their specific
> bootloader.
>
> This dri
Android userspace tells the kernel that it wants to boot into recovery
or some other non-default OS environment by passing a string argument
to reboot(). It is left to the OEM to hook this up to their specific
bootloader.
This driver uses the bootloader control block (BCB) in the 'misc'
partition,
13 matches
Mail list logo
