From: Sam Song <samlinuxppc@yahoo.com.cn>
To: Marius Groeger <mgroeger@sysgo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Meaning of BSP and LSP
Date: Thu, 14 Oct 2004 17:27:39 +0800 (CST) [thread overview]
Message-ID: <20041014092739.6826.qmail@web15601.mail.cnb.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410140952570.1661@mag.sysgo.com>
Marius Groeger <mgroeger@sysgo.com> wrote：
> 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
So that day the meaning of BSP was clear enough.
> "LSP" is a term introduced by MontaVista, AFAIR, so
> maybe one of the MV folks on this list wants to
> elaborate on this?
I also got the term "LSP" from MV.
> 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.
See what's EP view on "BSP".
http://www.embeddedplanet.com/products/bsp_linux.asp
It seems that BSP > = LSP.
Just as Wolfgang said, the meaning varys in different
vendors. But at least "LSP" by MV doesn't include
hardware scheme and boot loader code, I think.
"LSP" is a special term defined by MV. So just to
follow the meaning as MV does.
Thanks for your nice comment on this topic.
=====
Best regards,
Sam
_________________________________________________________
Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂
http://music.yisou.com/
美女明星应有尽有，搜遍美图、艳图和酷图
http://image.yisou.com
1G就是1000兆，雅虎电邮自助扩容！
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/
prev parent reply other threads:[~2004-10-14 9:27 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
2004-10-14 9:27 ` Sam Song [this message]
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=20041014092739.6826.qmail@web15601.mail.cnb.yahoo.com \
--to=samlinuxppc@yahoo.com.cn \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgroeger@sysgo.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