| 1 |
On 05/06/2014 03:07, Markos Chandras wrote: |
| 2 |
> @kumba: You mentioned too many times that I wanted to "drop" support for |
| 3 |
> mips3 and mips4. I never said that (I am sort-of tired keep repeating |
| 4 |
> that). All I said (again) was to reduce the frequency or stop building |
| 5 |
> them at all. Users can still get an existing mips3/mips4 stage3 and |
| 6 |
> update themselves |
| 7 |
|
| 8 |
Maybe it's just my way of interpretation, but in your opening paragraph, |
| 9 |
even though you said we wouldn't drop support, you did suggest not creating |
| 10 |
new stages for mips1-mips4. |
| 11 |
|
| 12 |
Given a sufficiently long-enough time, that effectively drops support due to |
| 13 |
bitrot. Like I mentioned w/ the 2009-era userland on this Octane, I am not |
| 14 |
going to even try to update that, simply due to the amount of time it would |
| 15 |
take, even if I figure the IRQ prioritization bugs out. |
| 16 |
|
| 17 |
So, my apologies if I read it wrong, but that's just how I see it. |
| 18 |
|
| 19 |
|
| 20 |
> (picking up a random thread) |
| 21 |
> |
| 22 |
> Ok thanks for the replies. |
| 23 |
> |
| 24 |
> Ok I think it's safe to proceed with the following: |
| 25 |
> - Stop mips1 builds (we don't have mips2) |
| 26 |
|
| 27 |
I'll defer to Matt to chime in to my last message and correct me anymore, if |
| 28 |
needed, but, I think we'll want to keep either a mips1 or a mips2, but not |
| 29 |
both. As well as decide whether it's a full stage3 or just a simple |
| 30 |
stage1/stage2 tarball so people have a base from which to start a port to a |
| 31 |
new MIPS machine if needed. That can get updated once a year, especially if |
| 32 |
it's a stage1 which shouldn't take long at all. |
| 33 |
|
| 34 |
|
| 35 |
> - Reduce the frequency to once-a-year for mips3 and mips4. Updating |
| 36 |
> these stages every year with catalyst will be a lot of fun ;) |
| 37 |
|
| 38 |
NAK, At least once every 6 months, and preferably shortly after the .1 |
| 39 |
release of a new major gcc rev, given gcc's absurd compile time now. Gentoo |
| 40 |
moves fast, and a lot can change in a year. |
| 41 |
|
| 42 |
Anyone looking to work with older SGI hardware needs something to start |
| 43 |
from, and if a stage3 is too old, it can take those machines a while to |
| 44 |
update everything. I know most others on the team don't care for the SGI |
| 45 |
hardware anymore, but it's still the most widely-available MIPS hardware for |
| 46 |
hobbyists and tinkerers. |
| 47 |
|
| 48 |
Otherwise, just e-mail me your mips3/mips4/mips4_r10 spec files, any custom |
| 49 |
tweaks/changes to catalyst, and any specific instructions you do |
| 50 |
before/during/after a catalyst build and I'll put the O2 to work if needed. |
| 51 |
|
| 52 |
-- |
| 53 |
Joshua Kinard |
| 54 |
Gentoo/MIPS |
| 55 |
kumba@g.o |
| 56 |
4096R/D25D95E3 2011-03-28 |
| 57 |
|
| 58 |
"The past tempts us, the present confuses us, the future frightens us. And |
| 59 |
our lives slip away, moment by moment, lost in that vast, terrible in-between." |
| 60 |
|
| 61 |
--Emperor Turhan, Centauri Republic |
Archives