Anthony Towns wrote:
>
> On Fri, Jun 01, 2001 at 11:41:26AM +0200, Giacomo Catenazzi wrote:
> > Anthony Towns wrote:
> > > On Thu, May 31, 2001 at 10:13:22AM +0200, Giacomo Catenazzi wrote:
> > > > The license (for non-FREE section):
> > > > / These microcode updates are distributed for the
On 01-Jun-01, 04:41 (CDT), Giacomo Catenazzi <[EMAIL PROTECTED]> wrote:
> Anthony Towns wrote:
> > Note that Intel's claims as to what you can and can't do with the
> > microcode aren't necessarily legally binding.
>
> I don't undertand this sentence.
The license cannot forbid actions that are
Steve Greenland <[EMAIL PROTECTED]>:
> On the other hand, if we can't modify, what purpose is served
> by us distributing it at all? It's available from the Intel
> website, right? It's just a file that gets installed by the loader,
> right? There's no integration issue.
There are two advantages
On 01-Jun-01, 16:02 (CDT), Raul Miller <[EMAIL PROTECTED]> wrote:
> [No one (other than Thomas Bushnell) is advocating that the microcode
> be distributed under the DFSG.]
Well, I think I would *advocate* that it be distributed under the
DFSG. I suspect that the benefits of doing so are perhaps l
On Fri, Jun 01, 2001 at 05:02:30PM -0400, Raul Miller wrote:
> > Contrib is an official part of Debian,
On Sat, Jun 02, 2001 at 04:33:32PM +1000, Anthony Towns wrote:
> Only in the same sense that non-free is (ie, it's not part of the Debian
> Distribution, but it's still distributed by the Debia
On Fri, Jun 01, 2001 at 05:02:30PM -0400, Raul Miller wrote:
> Contrib is an official part of Debian,
Only in the same sense that non-free is (ie, it's not part of the Debian
Distribution, but it's still distributed by the Debian project).
See item 1 of the social contract ``..., but we will nev
Um.. just to reiterate what's going on here:
For Debian to distribute the microcode at all, we need permission to
distribute it[1].
For Debian to distribute the microcode *as a part of Debian*, we'd need
the microcode to meet the DFSG.
[No one (other than Thomas Bushnell) is advocating that the
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> writes:
> Maybe, but there would be very little practical benefit from having
> DFSG-free microcode. Most of the arguments for free software don't
> really apply to microcode. I work for a company that designs
> microprocessors, so I might be interested in
On Fri, Jun 01, 2001 at 11:41:26AM +0200, Giacomo Catenazzi wrote:
> Anthony Towns wrote:
> > On Thu, May 31, 2001 at 10:13:22AM +0200, Giacomo Catenazzi wrote:
> > > The license (for non-FREE section):
> > > / These microcode updates are distributed for the sole
> > > purpose of
> > > /
Anthony Towns wrote:
>
> On Thu, May 31, 2001 at 10:13:22AM +0200, Giacomo Catenazzi wrote:
> > The license (for non-FREE section):
> > / Copyright Intel Corporation, 1995, 96, 97, 98, 99,
> > 2000, 2001.
> > /
> > / These microcode updates are distributed for the sole
> > purpose of
Giacomo Catenazzi <[EMAIL PROTECTED]>:
> But there is annother difficult. To write BIOS we use assembler because
> we have much control to hardware, to write microcode I think they don't
> use any language, to be more direct. They write (maybe) directly the bit
> or byte. Thus there exists only bi
Anthony Towns writes:
> It's not able to be modified, it's not going to be a part of Debian
> anyway. What's your point?
Ok, perhaps I misunderstood. Please forgive me...I was assuming that
it was being discussed here precisely because it might be part of
Debian. What exactly is its current st
"Thomas Bushnell, BSG" wrote:
>
> Giacomo Catenazzi <[EMAIL PROTECTED]> writes:
>
> > 2) It is difficult to say that microcode is a program:
> >there are surelly many entry points (one per instruction),
> >many exit point. Instruction are executed partly in parallel,...
> >It is too h
On Thu, May 31, 2001 at 02:55:50PM -0700, Thomas Bushnell, BSG wrote:
> Anthony Towns writes:
> > Adding something like: ``In addition, you may freely distribute copies of
> > this microcode'' would be fine. Adding something like ``Special permission
> > is given for this microcode to be distribut
> Anthony Towns writes:
>
> > Adding something like: ``In addition, you may freely distribute copies of
> > this microcode'' would be fine. Adding something like ``Special permission
> > is given for this microcode to be distributed by the Debian project.''
> > would probably also be fine.
>
> U
Anthony Towns writes:
> Adding something like: ``In addition, you may freely distribute copies of
> this microcode'' would be fine. Adding something like ``Special permission
> is given for this microcode to be distributed by the Debian project.''
> would probably also be fine.
Um, granting only
Giacomo Catenazzi <[EMAIL PROTECTED]> writes:
> 2) It is difficult to say that microcode is a program:
>there are surelly many entry points (one per instruction),
>many exit point. Instruction are executed partly in parallel,...
>It is too hardware dependent. You can see it also as a i
On Thu, May 31, 2001 at 10:13:22AM +0200, Giacomo Catenazzi wrote:
> The license (for non-FREE section):
> / Copyright Intel Corporation, 1995, 96, 97, 98, 99,
> 2000, 2001.
> /
> / These microcode updates are distributed for the sole
> purpose of
> / installation in the
"Thomas Bushnell, BSG" wrote:
>
> Giacomo Catenazzi <[EMAIL PROTECTED]> writes:
>
> > 1) Do this license allow us and the mirrors to distribute the
> > microcode?
>
> I don't believe so.
>
> > 3) Intel calls microcode "data file" (see the email from
> > Intel).
> >Thus no software, no restr
Thomas Bushnell, BSG <[EMAIL PROTECTED]>:
> > 3) Intel calls microcode "data file" (see the email from
> > Intel).
> >Thus no software, no restriction in GPL and DFSG (like
> > strictly copyright
> >for distribute a license) (and microcode is similar: you
> > can distribute,
> >but not
Giacomo Catenazzi <[EMAIL PROTECTED]> writes:
> 1) Do this license allow us and the mirrors to distribute the
> microcode?
I don't believe so.
> 3) Intel calls microcode "data file" (see the email from
> Intel).
>Thus no software, no restriction in GPL and DFSG (like
> strictly copyright
>
21 matches
Mail list logo
