i appreciate the help, i really do. but i have VERY little time anymore, and probably even less in the forthcoming, so i must request that a bit more effort be placed on the email communications front: 1) as is stated when you subscribe to the list, reply to the LIST and the LIST ONLY. unless there is a reason for a private reply, don't make it private. and there is NEVER a reason to CC anyone, subscribing is mandatory to posting, so all you do is screw up the threading (minimalist will skip sending to you if it notices your already in the To: or CC: headers). use list-reply to make this easy, if your MUA doesn't have list-reply, it sucks, get a new one that does, like mutt. or else don't complain to me that its hard, complain to the author of your MUA. theres only 3 headers in every post i make which makes this abundently easy. 2) since you obviously have more time then me, please put a bit more time into fully reading my post before replying, regarding the below i answered that question AT least 6 times (most were in private, see above). i don't have time to repeat myself. now Remco, you need to keep in mind that i have been putting a great deal of thought into the design of prom-libc and yaboot 2 for a LONG time (well over a year), i also have more experience and knowledge of how the firmware operates, and what it provides us (by all your admission). so with all due respect remember it is my project, and that means im going to guide the design direction, i AM open to changes in direction from what ive posted and described, but you NEED to fully describe your proposals in detail, and most importantly GOOD rationals. you can't just go and `decide' that things are going to be done differently and then start tossing code around with that assumption, it won't go far with me. some of your assumptions of design change simply won't work in practice, which is why you need to actually PROPOSE a change before assuming thats how it will be. and importantly such proposals need to happen here so the others can participate in the discussion. (see 1) 3) im not in a good mood at all this week, nothing to do with this project or any of you, so don't take my terse attitude in a personal or insulting way, nor as a indication of lack of appreciation for the help, without the help it will take years for me to complete this project, with help i think it could be done by next year. but again its just going to slow things down if i have to talk past you over and over again, so please try a little harder to read and understand my replies and then post well reasoned responses. thanks again. On Wed, Jul 09, 2003 at 10:38:58PM -0800, Ethan Benson wrote: > On Wed, Jul 09, 2003 at 11:30:29AM -0700, Remco Treffkorn wrote: > > On Wednesday 09 July 2003 02:17, Ethan Benson wrote: > > > On Tue, Jul 08, 2003 at 02:56:46PM -0700, Remco Treffkorn wrote: > > > > The attached tar file contains only files I have added or changed in > > > > libc. > > > > > > don't see any attachment.. > > > > > > > They say it's fully automatic, but in reality you have to push this bitton! > > > > > > The prom type in libc/Makefile is now > > > > PROM_TYPE := linux/$(ARCH) > > > > > > this is wrong. it should be PROM_TYPE := linux > > > > How do I distinuish between ppc, mips,... and i386? > > Although Linux, it is still platform specific. > > The same as with OF on ppc or sparc. > > i don't know how many times i have to keep saying this: > > sysdeps/linux > sysdeps/powerpc/linux > -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgp00018.pgp
Description: PGP signature