LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marius Groeger <mgroeger@sysgo.com>
To: Sam Song <samlinuxppc@yahoo.com.cn>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Meaning of BSP and LSP
Date: Thu, 14 Oct 2004 10:25:31 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0410140952570.1661@mag.sysgo.com> (raw)
In-Reply-To: <20041013193959.57540.qmail@web15605.mail.cnb.yahoo.com>

On Thu, 14 Oct 2004, Sam Song wrote:

> I'd like to make sure about the meaning of BSP and
> LSP. There is sth unclear in my mind, I am afraid.

>From what I know, the term BSP was coined as an acronym for "Board 
Support Package" in pre-Linux days. To me it is most familiar in 
conjunction with Embdedded (RT)OSes such as LynxOS, vxWorks, or pSOS 
and many others. These systems have a more or less clearly defined BSP 
API, meaning that a port to a new platform is a well defined process.

Grossly simplified, the BSP provider must implement a number of 
support functions which make hardware resources (interrupts, memory 
and so forth) available to the common kernel code. Note also that this 
is valid across architectures (PPC, ARM, X86...).

Linux still doesn't really offer something like this. Some people may 
argue that things are actually improving, but most people probably 
just don't care. The simplest reason I can think of for that is that 
there were always enough knowledgable people to do the hard porting 
work. Also, obviously, Linux doesn't care for commercial issues such 
like wanting to keep the common kernel code closed.

"LSP" is a term introduced by MontaVista, AFAIR, so maybe one of the 
MV folks on this list wants to elaborate on this?

Bottom line: BSP is an OS/Vendor specific term to capture the software 
components related to a specific board. It is a useful handle in 
project discussions, provided that all participants use the same 
notion.

Regards,
Marius

-- 
Marius Groeger <mgroeger@sysgo.com>
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com

  parent reply	other threads:[~2004-10-14  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041013191012.47D9A2BDD3@ozlabs.org>
2004-10-13 19:39 ` Meaning of BSP and LSP Sam Song
2004-10-13 20:03   ` Wolfgang Denk
2004-10-13 20:17     ` Sam Song
2004-10-14  8:25   ` Marius Groeger [this message]
2004-10-14  9:27     ` Sam Song

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=Pine.LNX.4.61.0410140952570.1661@mag.sysgo.com \
    --to=mgroeger@sysgo.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=samlinuxppc@yahoo.com.cn \
    /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