linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH v7 3/3] [POWERPC] MPC832x_RDB: update dts to use SPI1in QE, register mmc_spi stub
Date: Thu, 6 Sep 2007 16:25:27 +0200	[thread overview]
Message-ID: <d9d8f9d5d4107d9e313396cecf34257e@kernel.crashing.org> (raw)
In-Reply-To: <20070905114023.GA4072@localhost.localdomain>

>> The kernel is of course welcome to do so -- and this may be a valid
>> reason to attach pin information to specific device nodes, if it 
>> actually
>> saves a non-negligible amount of power -- but it's not a reason to 
>> force
>> the kernel to have to care by not setting things up in the firmware.
>
> Well, I might agree here. But to me it seems unnatural that I have to
> upgrade bootloader to use SPI -- I can already boot the kernel.
>
> Bootloader's duties are finished when kernel booted. And if already
> running kernel is unable to do something, it's not bootloader's fault
> anymore, but kernel's itself.

If the firmware failed to properly initialise the system into some
stable state, then yeah, it _is_ the firmware's fault.

> And from the practical point of view, upgrading bootloader is much
> more error-prone and risky for the users without proper rescue tools
> and knowledge.

Yeah well -- it's hardly rocket science to make this a very
reliable and safe procedure.

>  Kernel is easier to deploy after bug-fixing (and
> wrongly set up GPIO pin is a bug). That's why I tend to like "dumb
> and simple" bootloaders and do not hang up too much duties on it.

That's one of the ways it is done -- have a "dumb and simple"
recovery firmware that can install new versions of the "main"
firmware.

Anyway, we're getting very far off-topic now :-)


Segher

  parent reply	other threads:[~2007-09-06 14:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 13:45 [PATCH v4 0/2] SPI support for fsl_soc and mpc832x_rdb Anton Vorontsov
2007-08-21 13:47 ` [PATCH v4 1/2] [POWERPC] fsl_soc: add support for fsl_spi Anton Vorontsov
2007-08-21 13:47 ` [PATCH v4 2/2] [POWERPC] MPC832x_RDB: update dts to use SPI1 in QE, register mmc_spi stub Anton Vorontsov
2007-08-21 15:27 ` [PATCH v5 0/2] SPI support for fsl_soc and mpc832x_rdb Anton Vorontsov
2007-08-21 15:29   ` [PATCH v5 1/2] [POWERPC] fsl_soc: add support for fsl_spi Anton Vorontsov
2007-08-22 14:24     ` Kumar Gala
2007-08-21 15:29   ` [PATCH v5 2/2] [POWERPC] MPC832x_RDB: update dts to use SPI1 in QE, register mmc_spi stub Anton Vorontsov
2007-08-22 14:25     ` Kumar Gala
2007-08-22 14:22   ` [PATCH v5 0/2] SPI support for fsl_soc and mpc832x_rdb Kumar Gala
2007-08-22 14:54     ` [PATCH v6 " Anton Vorontsov
2007-08-22 14:57       ` [PATCH v6 1/2] [POWERPC] fsl_soc: add support for fsl_spi Anton Vorontsov
2007-08-23  3:24         ` Stephen Rothwell
2007-08-23 11:33           ` [PATCH v7 0/3] " Anton Vorontsov
2007-08-23 11:35             ` [PATCH v7 1/3] [POWERPC] QE lib: extern par_io_config_pin and par_io_data_set funcs Anton Vorontsov
2007-08-23 11:35             ` [PATCH v7 2/3] [POWERPC] fsl_soc: add support for fsl_spi Anton Vorontsov
2007-08-23 11:36             ` [PATCH v7 3/3] [POWERPC] MPC832x_RDB: update dts to use SPI1 in QE, register mmc_spi stub Anton Vorontsov
2007-08-30 21:06               ` Timur Tabi
2007-08-31 13:50                 ` [PATCH v7 3/3] [POWERPC] MPC832x_RDB: update dts to use SPI1in " Li Yang-r58472
2007-09-01 23:59                   ` Segher Boessenkool
2007-09-03 13:55                     ` Timur Tabi
2007-09-03 15:13                       ` Anton Vorontsov
2007-09-03 23:17                         ` Segher Boessenkool
2007-09-04 10:47                           ` Anton Vorontsov
2007-09-04 18:20                             ` Scott Wood
2007-09-04 20:15                               ` Vitaly Bordug
2007-09-05 11:40                               ` Anton Vorontsov
2007-09-05 13:21                                 ` Scott Wood
2007-09-07  1:15                                   ` David Gibson
2007-09-07  1:28                                     ` Timur Tabi
2007-09-06 14:25                                 ` Segher Boessenkool [this message]
2007-09-06 14:19                             ` Segher Boessenkool
2007-09-06 14:35                               ` Timur Tabi
2007-09-03 23:12                       ` Segher Boessenkool
2007-09-04  3:16                         ` Timur Tabi
2007-09-06 14:13                           ` Segher Boessenkool
2007-09-06 14:19                             ` Scott Wood
2007-09-06 14:29                               ` Segher Boessenkool
2007-09-07  3:37                             ` David Gibson
2007-08-22 14:57       ` [PATCH v6 2/2] [POWERPC] MPC832x_RDB: update dts to use SPI1 in " Anton Vorontsov
2007-08-22 15:01       ` [PATCH v6 0/2] SPI support for fsl_soc and mpc832x_rdb Kumar Gala
2007-08-22 15:13         ` Anton Vorontsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9d8f9d5d4107d9e313396cecf34257e@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).