From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: linux-omap-psp-2.6.32 breaks iscsi-target
Date: Mon, 30 Aug 2010 15:23:52 -0400 [thread overview]
Message-ID: <4C7C0548.5030803@balister.org> (raw)
In-Reply-To: <AANLkTi=OfvXtUvPcTjSvA=v=jXWWdjixgPQp9201jUpH@mail.gmail.com>
On 08/30/2010 02:49 PM, J. L. wrote:
> Why is it bad to expect all packages build for all the machine/distro
> ? I would think that would be a more "ideal" situation especially if
> its a supported machine and distro
It is not bad. But we have a lot of packages and the people maintaining
stuff have limited time. Hopefully the TI kernel guys can find a way to
fix the issue Frans pointed out.
Philip
>
>
>
> On Mon, Aug 30, 2010 at 11:40 AM, Philip Balister<philip@balister.org> wrote:
>> On 08/30/2010 02:35 PM, Frans Meulenbroeks wrote:
>>>
>>> 2010/8/30 Philip Balister<philip@balister.org>:
>>>>
>>>> On 08/30/2010 01:47 PM, Frans Meulenbroeks wrote:
>>>>>
>>>>> The current beagleboard angstrom and minimal distro's (and maybe
>>>>> others) use the linux-omap-psp_2.6.32.bb recipe to build the kernel.
>>>>
>>>> What is iscsi and why would I need it on the Beagleboard?
>>>
>>> http://stgt.sourceforge.net/
>>>
>>> the pacakge is from
>>> http://iscsitarget.sourceforge.net/
>>> It is used by tgt (http://stgt.sourceforge.net/)
>>>
>>> with it you can e.g. mount an iscsi disk.
>>> iscsi is for instance also supported by windows 7 and by various NAS-es.
>>> Its throughput is better than Samba or NFS.
>>>
>>> So for beagle it could act as mechanism to e.g. retrieve content from a
>>> NAS.
>>
>> So the trade off is a kernel that has the best chance of fully supporting
>> the OMAP3 peripherals, or attaching to a NAS that is windows centric.
>>
>> The point I am trying to make is we can't expect all packages to build for
>> every MACHINE/DISTRO combination. People have to make tradeoffs.
>>
>> Philip
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2010-08-30 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 17:47 linux-omap-psp-2.6.32 breaks iscsi-target Frans Meulenbroeks
2010-08-30 18:19 ` Philip Balister
2010-08-30 18:35 ` Frans Meulenbroeks
2010-08-30 18:40 ` Philip Balister
2010-08-30 18:49 ` J. L.
2010-08-30 19:23 ` Philip Balister [this message]
2010-08-30 19:35 ` J. L.
2010-08-30 19:52 ` Frans Meulenbroeks
2010-08-30 18:56 ` Frans Meulenbroeks
2010-08-30 19:27 ` Tom Rini
2010-08-31 8:30 ` Koen Kooi
2010-08-31 9:17 ` Frans Meulenbroeks
2010-08-31 9:32 ` Graeme Gregory
2010-08-31 10:35 ` Raffaele Recalcati
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=4C7C0548.5030803@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.