EV-64260-BP & GT64260 bi_recs
Quoted 1 line · Tom Rini
Sure there is, for it to be accepted.
Wait a minute, why am I even talking to you? Mark said he is the responsible maintainer and promised to push my patch in a few days if there is no consensus by then, and I think I'll just wait a few days and then ask him to stick to his word. (I'm willing to bet $50 that in the next few days there will be no consensus nor will anyone else offer a counterpatch.)
Quoted 2 lines
And would you please make it
versus the_galileotree
Sorry, no, that would be a step backward and we need to move forward.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 5 lines · Michael Sokolov
Quoted 1 line · Tom Rini
Sure there is, for it to be accepted.
Wait a minute, why am I even talking to you?
Because you enjoy our conversations? :)
Quoted 4 lines
Mark said he is the responsible
maintainer and promised to push my patch in a few days if there is no consensus by then, and I think I'll just wait a few days and then ask him to stick to his word.
And then you'll have to go and improve the patch anyhow, if you're going to stick to your word. :)
Quoted 7 lines
(I'm willing to bet $50 that in the next few days there will be no consensus nor will anyone else offer a counterpatch.)
Quoted 2 lines
And would you please make it
versus the_galileotreeSorry, no, that would be a step backward and we need to move forward.
How is that a step backward? All of the current galileo work is in that tree. And a quick diff of the enet drivers in the two trees shows a good deal of differences, many of which aren't just cosmetic. Isn't it more 'natural' to update the most up to date file?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 10 lines · Michael Sokolov
Quoted 1 line · Tom Rini
Sure there is, for it to be accepted.
Wait a minute, why am I even talking to you? Mark said he is the responsible maintainer and promised to push my patch in a few days if there is no consensus by then, and I think I'll just wait a few days and then ask him to stick to his word. (I'm willing to bet $50 that in the next few days there will be no consensus nor will anyone else offer a counterpatch.)
Well, If I remember right, Mark doesn't even have a galileo board anymore (someone else got it). So I could probably make an argument I'm the maintainer now.
Quoted 5 lines
Quoted 3 lines
And would you please make it
versus the_galileotreeSorry, no, that would be a step backward and we need to move forward.
I strongly suggest you submit me (or the -galileo) list patches, otherwise when I start merging the _galileo tree code to _devel, I'm likely to blow your changes away because I can't test them.
And PLEASE give me a different eth driver ;)
The one in the tree right now works for single cpus, but
a) is ugly
b) blows up very nicely with SMP.
The _galileo tree was created to keep us from thrashing in _devel with a bunch of crappy (but working) code.
FYI, I am about ready to merge Zuma's gt64260_mpsc driver to 2_4_devel since it seems to work reasonably well, and the code is mostly sane. If you have another mpsc driver, speak now or forever hold your peace.
--
Troy Benjegerdes | master of mispeeling | 'da hozer' | [email protected] -----"If this message isn't misspelled, I didn't write it" -- Me ----- "Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Schulz
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 3 lines · Troy Benjegerdes
Well, If I remember right, Mark doesn't even have a galileo board anymore (someone else got it). So I could probably make an argument I'm the maintainer now.
Mine broke. I'm supposed to get one yesterday/today/tomorrow. No FedEx guy so far today...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Now that things are settling down a bit -- who's got which tree running on which platform and in what condition? Basically, what's the conditon of the 2_4_galileo and 2_4_devel tree's on EVB, MVP, (etc) -- SMP y/n, PCI cards (scsi, ide, etc) y/n, running solid y/n, and under which boot environment (dink, ppcboot, starmon, etc)?
Quoted 8 lines
Quoted 3 lines · Troy Benjegerdes
Well, If I remember right, Mark doesn't even have a galileo board anymore (someone else got it). So I could probably make an argument I'm the maintainer now.
Mine broke. I'm supposed to get one yesterday/today/tomorrow. No FedEx guy so far today...
--
Sincerely,
Jim Potter
45th Parallel Processing
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 4 lines · Jim Potter
Now that things are settling down a bit -- who's got which tree running on which platform and in what condition? Basically, what's the conditon of the 2_4_galileo and 2_4_devel tree's on EVB, MVP, (etc) -- SMP y/n, PCI cards (scsi, ide, etc) y/n, running solid y/n, and under which boot environment (dink, ppcboot, starmon, etc)?
I have _gal and _devel running on the EVB and _gal running our custom board with ppcboot. Both are stable; the _gal has a bunch of other stuff and random bug fixes in it. _devel does not work on our custom board due to ethernet bugs, mpsc problems, and no 750cx support. _devel does also not work 100% with ppcboot since it does not support bd_info afaik.
We are using the 750cx(e). We do not use DINK. We do have an Abatron.
Note that our evb is showing signs of breaking (the cpu module slot seems to be a real weak point), so we may end up just like Mark any second now.
--
Nye Liu
[email protected]
"Who would be stupid enough to quote a fictitious character?"
-- Don Quixote
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 2 lines · Nye Liu
Note that our evb is showing signs of breaking (the cpu module slot seems to be a real weak point), so we may end up just like Mark any second now.
Yep, mine broke when switching cpu's. Was supporting it underneath & everything but I guess I did it one too many times...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/