public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp@bsdimp•com>
To: wmb@firmworks•com
Cc: nico@fluxnic•net, microblaze-uclinux@itee•uq.edu.au,
	devicetree-discuss@lists•ozlabs.org, jamie@shareable•org,
	linuxppc-dev@ozlabs•org, mike@compulab•co.il,
	ppc6dev@digitaldans•com, jeremy.kerr@canonical•com,
	linux-arm-kernel@lists•infradead.org
Subject: Re: Request review of device tree documentation
Date: Wed, 16 Jun 2010 00:52:37 -0600 (MDT)	[thread overview]
Message-ID: <20100616.005237.338122493954307067.imp@bsdimp.com> (raw)
In-Reply-To: <4C187013.5000400@firmworks.com>

In message: <4C187013.5000400@firmworks•com>
            Mitch Bradley <wmb@firmworks•com> writes:
: Mike Rapoport wrote:
: > Mitch Bradley wrote:
: >> Mike Rapoport wrote:
: >>> Mitch Bradley wrote:
: >>>
: >>>> The second topic is the hypothetical use of OFW as a HAL. That will
: >>>> not happen for several reasons.  The opposition to the idea is
: >>>> widespread and deeply held, and there are good arguments to support
: >>>> that opposition.  Furthermore, the economic conditions necessary for
: >>>> the creation of such a HAL do not exist in the ARM world, nor indeed
: >>>> in the Linux world in general.  (The necessary condition is the
: >>>> ability for one company to impose a substantial change by fiat -
: >>>> essentially a monopoly position.)
: >>>>
: >>>> Shall we agree, then, that any further discussion of the HAL issue is
: >>>> "just for fun", and that nobody needs to feel threatened that it would
: >>>> actually happen?
: >>>
: >>> I've recently worked with vendor versions of U-Boot for advanced ARM
: >>> SoCs. There is already *huge* chunk of HAL code in those versions. And
: >>> if there would be possibility to have callbacks into the firmware
: >>> these chunks would only grow, IMHO.
: >>
: >> How can there be HAL code in U-Boot unless there is already the
: >> possibility to have callbacks into the firmware?
: >
: > Currently it aims to abstract hardware from U-Boot and reuse the same
: > HW access code across operating systems and bootloaders. If this code
: > would have callbacks I afraid the things would became worse.
: 
: The only way I can understand what you said is if I assume that by
: "callback", you mean the following sequence:
: 
: a) U-boot loads and executes the OS, providing to the OS the address
: of some HW access routines that it can use
: b) The OS calls one of those HW access routines
: c) During the execution of that HW access routine, that routine calls
: "back" into the OS, before returning.  So a call into the OS is nested
: inside a call into U-boot resident code.
: 
: If that is what you are worried about, it is not what we were
: discussing.  We were discussing - and many people were against - step
: (b).
: 
: Are you saying that step (b) - the OS calling into routines provided
: by U-Boot - is already the status quo?

I don't know about status quo, but it certainly is supported.  There's
an option to allow for a secondary boot loader, such as FreeBSD's
/boot/loader, to call back into uboot to read things from
flash/disk/whatever, do network access, etc.  Not so much a HAL, but
more of an echo of the functionality provided by PC BIOS functions.
/boot/loader can be viewed as a mini OS that calls back into uboot to
have it do things.  Once /boot/loader loads FreeBSD, btw, it and uboot
disappear from the scene, so this isn't exactly a HAL situation...

Warner


: >
: >> It is not HAL if it can't be called.
: >>
: >>>
: >>>
: >>>> The potential for "vendors breaking out of the debugging use case and
: >>>> turning it into a HAL" is miniscule, because
: >>>>
: >>>> a) The callback is disabled by default
: >>>> b) The technical challenges of the callback interface limit its
: >>>> applicability to specific "wizard user" scenarios
: >>>> c) OFW is unlikely to achieve sufficient market penetration for the
: >>>> HAL thing to be worth doing
: >>>>
: >>>>
: >>>> _______________________________________________
: >>>> linux-arm-kernel mailing list
: >>>> linux-arm-kernel@lists•infradead.org
: >>>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
: >>>
: >>>
: >
: >
: _______________________________________________
: devicetree-discuss mailing list
: devicetree-discuss@lists•ozlabs.org
: https://lists.ozlabs.org/listinfo/devicetree-discuss
: 
: 

  parent reply	other threads:[~2010-06-16  7:03 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 22:59 Request review of device tree documentation Grant Likely
2010-06-11 23:47 ` Dan Malek
2010-06-12  2:58   ` Benjamin Herrenschmidt
2010-06-12  4:48     ` Mitch Bradley
2010-06-12  6:53   ` Grant Likely
2010-06-12  8:19     ` Mitch Bradley
2010-06-12 10:45       ` Benjamin Herrenschmidt
2010-06-12 10:48         ` Benjamin Herrenschmidt
2010-06-12 16:30           ` Mitch Bradley
2010-06-12 22:52             ` Benjamin Herrenschmidt
2010-06-13  5:07               ` Grant Likely
2010-06-13  5:39                 ` Mitch Bradley
2010-06-13  5:59                   ` Benjamin Herrenschmidt
2010-06-13  6:45                     ` Mitch Bradley
2010-06-13  8:29                       ` Benjamin Herrenschmidt
2010-06-14  5:36                         ` Grant Likely
2010-06-14 20:00                           ` Ben Dooks
2010-06-13  8:57                       ` Benjamin Herrenschmidt
2010-06-14  5:23                     ` Grant Likely
2010-06-14  7:38                       ` Russell King - ARM Linux
2010-06-14  7:45                         ` Mitch Bradley
2010-06-14  9:25                           ` Russell King - ARM Linux
2010-06-14  9:36                             ` Benjamin Herrenschmidt
2010-06-14  9:47                               ` Russell King - ARM Linux
2010-06-14 14:29                                 ` Jamie Lokier
2010-06-14 13:51                       ` Nicolas Pitre
2010-06-14 15:35                         ` Grant Likely
2010-06-14 15:58                           ` Nicolas Pitre
2010-06-14 16:16                             ` Grant Likely
2010-06-14  5:02                   ` Grant Likely
2010-06-14 12:44                     ` David Gibson
2010-06-14 14:59                       ` Nicolas Pitre
2010-06-14 15:08                         ` Grant Likely
2010-06-14 16:02                         ` Jamie Lokier
2010-06-14 16:23                           ` Nicolas Pitre
2010-06-14 16:29                             ` Grant Likely
2010-06-14 16:28                           ` Grant Likely
2010-06-14 16:33                             ` Jamie Lokier
2010-06-14 16:58                           ` Mitch Bradley
2010-06-14 17:26                             ` Nicolas Pitre
2010-06-14 18:20                               ` Mitch Bradley
2010-06-14 19:40                                 ` Nicolas Pitre
2010-06-14 20:08                                   ` Mark Brown
2010-06-16  6:09                             ` Mike Rapoport
2010-06-16  6:13                               ` Mitch Bradley
2010-06-16  6:17                                 ` Mike Rapoport
2010-06-16  6:32                                   ` Mitch Bradley
2010-06-16  6:47                                     ` Mike Rapoport
2010-06-16  7:40                                       ` Mitch Bradley
2010-06-16  9:45                                         ` Vladimir Pantelic
2010-06-16 10:39                                         ` Mike Rapoport
2010-06-16 11:41                                           ` Jamie Lokier
2010-06-16 13:48                                             ` Jamie Bennett
2010-06-16 14:39                                           ` Nicolas Pitre
2010-06-16 17:43                                             ` Tim Bird
2010-06-16  6:52                                     ` M. Warner Losh [this message]
2010-06-18 22:12                                       ` Frank Rowand
2010-06-15  2:02                         ` David Gibson
2010-06-14 15:51                       ` M. Warner Losh
2010-06-13  5:48                 ` Benjamin Herrenschmidt
2010-06-14  5:13                   ` Grant Likely
2010-06-14  6:09                     ` Benjamin Herrenschmidt
2010-06-14  6:17                       ` Mitch Bradley
2010-06-12 22:15     ` Olof Johansson
2010-06-12 23:09       ` Grant Likely
2010-06-13  6:47         ` [microblaze-uclinux] " Edgar E. Iglesias
2010-06-12  3:00 ` Benjamin Herrenschmidt
2010-06-12  3:07   ` Benjamin Herrenschmidt
2010-06-13 13:12     ` Jeremy Kerr
2010-06-14  5:40       ` Grant Likely
2010-06-12 17:33 ` Stephan Gatzka
2010-06-12 18:19   ` Grant Likely
2010-06-14  5:54   ` Grant Likely
2010-08-05  4:43 ` David Gibson
2010-09-01 16:19   ` Grant Likely

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=20100616.005237.338122493954307067.imp@bsdimp.com \
    --to=imp@bsdimp$(echo .)com \
    --cc=devicetree-discuss@lists$(echo .)ozlabs.org \
    --cc=jamie@shareable$(echo .)org \
    --cc=jeremy.kerr@canonical$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
    --cc=mike@compulab$(echo .)co.il \
    --cc=nico@fluxnic$(echo .)net \
    --cc=ppc6dev@digitaldans$(echo .)com \
    --cc=wmb@firmworks$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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