Hi,
(First of all: I'm not sure this list is the right place to ask. If it
is not, feel free to point me in the right direction)
Is there a specific reason why the kernel on the install media is built
with CONFIG_USB_STORAGE_DEBUG=y ? This has the nasty side-effect of
completely overwriting
On 2010.12.11 09:26, Andrea Conti wrote:
> Hi,
>
> (First of all: I'm not sure this list is the right place to ask. If
> it
>
> is not, feel free to point me in the right direction)
>
> Is there a specific reason why the kernel on the install media is
> built
> with CONFIG_USB_STORAGE_DEBUG=y
Hi all,
bugs like [1] makes clear to me that the increasing number of CPU
extensions USE flags is getting more and more confusing.
ffmpeg-0.6_p25767.ebuild : IUSE="+3dnow +3dnowext alsa altivec amr
bindist +bzip2 cpudetection custom-cflags debug dirac doc +encode faac
frei0r gsm +hardcoded-
On 12/11/10 18:57, Jeroen Roovers wrote:
> Hi all,
>
>
> bugs like [1] makes clear to me that the increasing number of CPU
> extensions USE flags is getting more and more confusing.
>
[snip]
>
> Among all CPU extensions USE flags you'll find:
>
> 3dnow
> 3dnowext
> mmx
> mmxext
> sse
> s
On Sat, 11 Dec 2010 19:19:05 +0100
Patrick Lauer wrote:
> How many packages are affected by those?
> I like the idea, but I think changing it around for 2 packages might
> be a bit silly. If there's a reasonable amount of packages involved
> I'm all for it.
How many packages use VIDEO_CARDS? How
On Sat, Dec 11, 2010 at 5:57 PM, Jeroen Roovers wrote:
[snip]
I agree that this could be better. To me, most of the problems with
this are due to users not knowing which of these should be set for
their particular CPU.
Instead of having defaults set by a profile, I'd like to figure out a
way we
On Sat, Dec 11, 2010 at 20:01, Matt Turner wrote:
> I agree that this could be better. To me, most of the problems with
> this are due to users not knowing which of these should be set for
> their particular CPU.
>
> Instead of having defaults set by a profile, I'd like to figure out a
> way we ca
On Sat, 11 Dec 2010 18:57:58 +0100
Jeroen Roovers wrote:
> bugs like [1] makes clear to me that the increasing number of CPU
> extensions USE flags is getting more and more confusing.
Another big confusion is that x86 and amd64 use the same names for many
extensions, but often the archs require d
On Saturday, December 11, 2010 12:57:58 Jeroen Roovers wrote:
> but more like this:
>
> [ebuild N] media-video/ffmpeg-0.6_p25767 USE="bzip2 encode
> hardcoded-tables zlib -X -alsa (-altivec) -amr -bindist -cpudetection
> -custom-cflags -debug -dirac -doc -faac -frei0r -gsm -ieee1394 -jack
>
Dirkjan Ochtman posted on Sat, 11 Dec 2010 20:03:39 +0100 as excerpted:
> On Sat, Dec 11, 2010 at 20:01, Matt Turner wrote:
>> I agree that this could be better. To me, most of the problems with
>> this are due to users not knowing which of these should be set for
>> their particular CPU.
>>
>> I
On Sat, 11 Dec 2010 18:57:58 +0100
Jeroen Roovers wrote:
> Among all CPU extensions USE flags you'll find:
>
> 3dnow
> 3dnowext
> mmx
> mmxext
> sse
> sse2
> sse3
> sse4
> sse4a
> sse5
> ssse3
>
> I probably missed a few, there.
sse4.1, sse4.2, avx
sse5 was a draft, it was never implemented.
On Sat, 11 Dec 2010 19:01:16 +
Matt Turner wrote:
> On Sat, Dec 11, 2010 at 5:57 PM, Jeroen Roovers wrote:
> [snip]
>
> I agree that this could be better. To me, most of the problems with
> this are due to users not knowing which of these should be set for
> their particular CPU.
>
> Inste
12 matches
Mail list logo
