On 29-06-17, 13:50, Russell King - ARM Linux wrote:
> On Thu, Jun 29, 2017 at 09:21:57AM +0530, Viresh Kumar wrote:
> > On 28-06-17, 08:55, Randy Dunlap wrote:
> > > On 06/28/2017 03:26 AM, Viresh Kumar wrote:
> >
> > > > +config BOOT_CONSTRAINTS
> > > > + bool "Boot constraints for devices"
On Thu, Jun 29, 2017 at 09:21:57AM +0530, Viresh Kumar wrote:
> On 28-06-17, 08:55, Randy Dunlap wrote:
> > On 06/28/2017 03:26 AM, Viresh Kumar wrote:
>
> > > +config BOOT_CONSTRAINTS
> > > + bool "Boot constraints for devices"
> > > + default y
> >
> > Why default y?
> >
> > As Linus just wrot
On 28-06-17, 08:55, Randy Dunlap wrote:
> On 06/28/2017 03:26 AM, Viresh Kumar wrote:
> > +config BOOT_CONSTRAINTS
> > + bool "Boot constraints for devices"
> > + default y
>
> Why default y?
>
> As Linus just wrote yesterday:
>
> No. We've tried. The only sensible default (and that I try t
On 06/28/2017 03:26 AM, Viresh Kumar wrote:
> Some devices are powered ON by the bootloaders before the bootloader
> handovers control to Linux. It maybe important for those devices to keep
> working until the time a Linux device driver probes the device and
> reconfigure its resources.
>
> A typi
Some devices are powered ON by the bootloaders before the bootloader
handovers control to Linux. It maybe important for those devices to keep
working until the time a Linux device driver probes the device and
reconfigure its resources.
A typical example of that can be the LCD controller, which is
5 matches
Mail list logo
