Mail Archives: djgpp/2000/03/03/22:20:19
Bill Currie wrote:
> I've cc'd this to all appearently interested parties, including the list. Please keep me in the loop as I already get too much mail to sift through djgpp as well.
>
> On Thu, Mar 02, 2000 at 07:35:06AM -0600, Jeff Williams wrote:
> > Bill,
> >
> > There's been some activity of late on the djgpp list regarding your
> > bcserio package. I'm forwarding this particular posting for your
> > information, since I think I remember you saying you didn't follow the
> > list any longer.
>
> Thanks. I'm glad you let me know, and thanks for including the patch in the forward.
>
> I'm sorry I never updated the package on simtel, especially as my
> email has changed to bill AT taniwha DOT org (this should be permanent).
In the DJGPP FAQ, version 2.11, I found 3 different (and probably
wrong) addresses for you which made it hard for us to contact you
directly. Unless this has already been fixed in a newer version, I
suggest to do so...
> > I'm not subscribed to the DJGPP list, so please CC any replies.
> >
> > > On 27 Feb 00, at 10:09, Peter Gerwinski wrote:
> > >
> > > > Hello,
> > > >
> > > > we would like to use Bill Currie's `serio' module in GPLed and
> > > > non-GPLed projects.
>
> This is ok by me. I prefer GPL these days, but when I released
> bcserio, I was undecided, so it's almost public domain. I also did
> not understand that releasing something without a license means
> `all rights reseverd'. This was not the intention. So long as any
> changes to bcserio continue to be shared, use it as you wish.
The LGPL guarantees that any changes to bcserio will have to be
shared, and it makes it possible to use it in GPLed and non-GPLed
projects as Peter needs to.
Another license that would be fine for us is GPL with the following
exception. That's what libc uses, and what we use for most of GPC's
units.
: As a special exception, if you link this library with files compiled
: with a GNU compiler to produce an executable, this does not cause
: the resulting executable to be covered by the GNU General Public
: License. This exception does not however invalidate any other
: reasons why the executable file might be covered by the GNU
: General Public License.
> I beleive it was more broken than that code snippet implies. For one, I forgot to save esi.
Yes, I fixed this in my patch as well.
> > Yes, I discovered some more problems. I'm attaching my diffs with
> > yours integrated.
>
> I've put the latest version (not including your patches) onto my
> website: http://www.taniwha.org/serio.zip and I think you will
> want to see if I've fixed anything you haven't. Also, I updated my email in the README file :)
You made some changes I didn't. I think some improvements in the
hardware interfacing, but I didn't check exactly since I don't know
the ports etc. too well.
> > Also, I think that the need for the separate linker script can be
> > quite easily circumvented by declaring dummies before and after the
> > critical code and data and use their addresses for locking, rather
> > than the linker-resolved symbols. I did that, and it seems to work.
> > Are there any problems with that method?
>
> Yeah, it's messy:). I did it that way originally. better yet is to
> just merge the script I supplied (note, it may be out of date, it
> was ok for djgpp 2.02) with the one that comes with djgpp (or is it built into ld?)
You mean the linker script? Well, as I said, my method requires no
special linker script at all, so unless there's a problem with my
method that I don't know of, I'd prefer this.
> Thanks for the patch, I'll go over it and try to merge it with my
> code, unless you beat me to it and send me a new patch:)
I've got no big ambitions to beat you. ;-) Since it's your code and
you know it better than I do, I think it's better if you merge my
patch (which shouldn't be difficult, I hope).
Frank
--
Frank Heckenbach, frank AT g-n-u DOT de
http://fjf.gnu.de/
PGP and GPG keys: http://fjf.gnu.de/plan
- Raw text -