Re: [OpenBIOS] Licensing of the code.

[David Woodhouse]

I said:
> I believe that we could use the LGPL for this.

[e-mail] said:
> The problem comes in if they have to directly modify any of our
> libraries. Since this is so low-level it may be impossible to work
> around them in some situations.

Then let them produce their own copy of the offending module - they're going 
to be fairly small modules anyway, so it shouldn't be too much of a hardship.

I appreciate that's not particularly ideal, but I suspect it might be the best 
we can do.
----                              ----                              ----
David Woodhouse, Robinson College, CB3 9AN, England.   ([phone]
    [e-mail]        http://dwmw2.robinson.cam.ac.uk
        finger [e-mail] for PGP key.

---
OpenBIOS -- http://www.linkscape.net/openbios/
[e-mail]   Body: un/subscribe
Problems?  [e-mail]

Licensing of the code.

[Dave Cinege]

David Woodhouse wrote:
> I said:
> > I believe that we could use the LGPL for this.
>
> [e-mail] said:
> > The problem comes in if they have to directly modify any of our
> > libraries. Since this is so low-level it may be impossible to work
> > around them in some situations.
>
> Then let them produce their own copy of the offending module - they're going
> to be fairly small modules anyway, so it shouldn't be too much of a hardship.
>
> I appreciate that's not particularly ideal, but I suspect it might be the best
> we can do.

I guess I'm going to have to agree with this.

---
OpenBIOS -- http://www.linkscape.net/openbios/
[e-mail]   Body: un/subscribe
Problems?  [e-mail]

Licensing of the code.

[Dean Gaudet]

I think a big sticking point will be the license Intel requires for the
microcode update software.  That license may dictate the license you'll
have to use for this project.  In fact that license may even preclude a
free software project.

Without the microcode updates you may have a hard time supporting intel
chips.

Dean

---
OpenBIOS -- http://www.linkscape.net/openbios/
[e-mail]   Body: un/subscribe
Problems?  [e-mail]

Licensing of the code.

[Dave Cinege]

Dean Gaudet wrote:
> I think a big sticking point will be the license Intel requires for the
> microcode update software.  That license may dictate the license you'll
> have to use for this project.  In fact that license may even preclude a
> free software project.
>
> Without the microcode updates you may have a hard time supporting intel
> chips.

I never heard of this before. What does this microcode bios code do?
It is just used for updating it?

---
OpenBIOS -- http://www.linkscape.net/openbios/
[e-mail]   Body: un/subscribe
Problems?  [e-mail]

Licensing of the code.

[Dean Gaudet]

See http://www.techweb.com/wire/news/june/0629bug.html for example. 
There's probably a press release on intel's site, but I can't be bothered
to wait for their pages to load, they seem to be running real slow today.

Dean

On Thu, 19 Feb 1998, Dave Cinege wrote:
> Dean Gaudet wrote:
> > I think a big sticking point will be the license Intel requires for the
> > microcode update software.  That license may dictate the license you'll
> > have to use for this project.  In fact that license may even preclude a
> > free software project.
> >
> > Without the microcode updates you may have a hard time supporting intel
> > chips.
>
> I never heard of this before. What does this microcode bios code do?
> It is just used for updating it?
>
> OpenBIOS -- http://www.linkscape.net/openbios/
> [e-mail]   Body: un/subscribe
> Problems?  [e-mail]

---
OpenBIOS -- http://www.linkscape.net/openbios/
[e-mail]   Body: un/subscribe
Problems?  [e-mail]