kill off PC9800
Randy.Dunlap" <[email protected]> wrote:
>
> PC9800 sub-arch is incomplete, hackish (at least in IDE), maintainers > don't reply to emails and haven't touched it in awhile.
And the hardware is obsolete, isn't it? Does anyone know when they were last manufactured, and how popular they are?
Hey, just being obsolete is no grounds for eliminating a subarchitecture...
However, I would have to say that being unmaintained is. Because of the penchant of x86 people to go "it compiles on my PC, ship it", the x86 subarchitectures are about the fastest bitrotting pieces of the kernel there are.
Since mach-pc9800 cannot currently be compiled and there's no evidence that it actually was, I'd remove it unless someone steps up quickly to maintain it (and get it to the point where it's actually compileable).
James
Quoted 11 lines · James Bottomley
Randy.Dunlap" <[email protected]> wrote:
>
> PC9800 sub-arch is incomplete, hackish (at least in IDE), maintainers > don't reply to emails and haven't touched it in awhile.And the hardware is obsolete, isn't it? Does anyone know when they were last manufactured, and how popular they are?
Hey, just being obsolete is no grounds for eliminating a subarchitecture...
Well it's a question of whether we're likely to see increasing demand for it in the future. If so then it would be prudent to put some effort into fixing it up rather than removing it.
Seems that's not the case. I don't see a huge rush on this but if after this discussion nobody steps up to take care of the code over the next few weeks, it's best to remove it.
Quoted 7 lines · Andrew Morton
Well it's a question of whether we're likely to see increasing demand for [pc9800] in the future. If so then it would be prudent to put some effort into fixing it up rather than removing it.
Seems that's not the case. I don't see a huge rush on this but if after this discussion nobody steps up to take care of the code over the next few weeks, it's best to remove it.
Although I like deleting things as much as the next guy :) I do have a question, to which I haven't come up with a good answer myself:
Should PC9800 be excised en masse, or just toss the obviously broken or not-in-any-makefile/Kconfig pieces?
The PC9800 net driver stuff still seems to build, and be sane.
Jeff
Quoted 7 lines · Jeff Garzik
Although I like deleting things as much as the next guy :) I do have a question, to which I haven't come up with a good answer myself:
Should PC9800 be excised en masse, or just toss the obviously broken or not-in-any-makefile/Kconfig pieces?
The PC9800 net driver stuff still seems to build, and be sane.
I haven't looked at the net stuff but if it's like the SCSI stuff, it's only usable in a pc9800. The vanilla kernel currently has no way to select a pc9800 subarchitecture build.
This is a test of interest. Since the pc9800 can't build the vanilla kernel, is anyone maintaining the out of tree pieces to allow it to build, and would they take on the job of maintaining it in-tree? if no-one's interested in maintaining the pc9800 subarchitecture components, it stands to reason that no-one is going to be compiling or running the net or scsi drivers, so there's no point keeping them hanging around. Thus, if one piece goes, they all should.
James
Quoted 13 lines · James Bottomley
Quoted 5 lines · Jeff Garzik
Although I like deleting things as much as the next guy :) I do have a question, to which I haven't come up with a good answer myself:
Should PC9800 be excised en masse, or just toss the obviously broken or not-in-any-makefile/Kconfig pieces?
The PC9800 net driver stuff still seems to build, and be sane.
I haven't looked at the net stuff but if it's like the SCSI stuff, it's only usable in a pc9800. The vanilla kernel currently has no way to select a pc9800 subarchitecture build.
Quoted 7 lines
This is a test of interest. Since the pc9800 can't build the vanilla kernel, is anyone maintaining the out of tree pieces to allow it to build, and would they take on the job of maintaining it in-tree? if no-one's interested in maintaining the pc9800 subarchitecture components, it stands to reason that no-one is going to be compiling or running the net or scsi drivers, so there's no point keeping them hanging around. Thus, if one piece goes, they all should.
Yeah, I suppose I agree, though I dislike removing it en masse for some reason. No real technical reason, more just gut feeling... The PC9800 people spent a good long while working with Alan and others to get what little bits got merged into the kernel.
I suppose disappearing and not maintaining the code is the overriding factor here...
Jeff
Quoted 13 lines · Andrew Morton
Quoted 11 lines · James Bottomley
Randy.Dunlap" <[email protected]> wrote:
>
> PC9800 sub-arch is incomplete, hackish (at least in IDE), maintainers > don't reply to emails and haven't touched it in awhile.And the hardware is obsolete, isn't it? Does anyone know when they were last manufactured, and how popular they are?
Hey, just being obsolete is no grounds for eliminating a subarchitecture...
Quoted 7 lines
Well it's a question of whether we're likely to see increasing demand for it in the future. If so then it would be prudent to put some effort into fixing it up rather than removing it.
Seems that's not the case. I don't see a huge rush on this but if after this discussion nobody steps up to take care of the code over the next few weeks, it's best to remove it.
Perhaps a nicer way to do this is to add a compile warning or error:
#warning "arch/i386/mach-pc9800 unmaintained since xx/xx/xx, nominated for removal xx/xx/xx if unclaimed"
..where the second date is, say, 3+ months after the warning goes in. Then people can nominate stuff for removal with one liners and users will get ample opportunity to complain.
Signature · 1 line
Matt Mackall : http://www.selenic.com : Linux development and consulting
Quoted 24 lines · Matt Mackall
Quoted 13 lines · Andrew Morton
Quoted 10 lines · James Bottomley
Quoted 3 lines · Randy.Dunlap
PC9800 sub-arch is incomplete, hackish (at least in IDE), maintainers don't reply to emails and haven't touched it in awhile.
And the hardware is obsolete, isn't it? Does anyone know when they were last manufactured, and how popular they are?
Hey, just being obsolete is no grounds for eliminating a subarchitecture...
Quoted 7 lines
Well it's a question of whether we're likely to see increasing demand for it in the future. If so then it would be prudent to put some effort into fixing it up rather than removing it.
Seems that's not the case. I don't see a huge rush on this but if after this discussion nobody steps up to take care of the code over the next few weeks, it's best to remove it.
Quoted 9 lines
Perhaps a nicer way to do this is to add a compile warning or error:
#warning "
arch/i386/mach-pc9800unmaintained since xx/xx/xx, nominated for removal xx/xx/xx if unclaimed"..where the second date is, say, 3+ months after the warning goes in. Then people can nominate stuff for removal with one liners and users will get ample opportunity to complain.
You're missing the point that this code doesn't compile *at all*. Nobody would ever see the warning.
--
Brian Gerst
Quoted 33 lines · Brian Gerst
Quoted 31 lines · Matt Mackall
Quoted 15 lines · Andrew Morton
Quoted 4 lines · James Bottomley
Quoted 2 lines · Randy.Dunlap
PC9800 sub-arch is incomplete, hackish (at least in IDE),
maintainers
Quoted 8 lines
Quoted 1 line
don't reply to emails and haven't touched it in awhile.
And the hardware is obsolete, isn't it? Does anyone know when they were
last manufactured, and how popular they are?Hey, just being obsolete is no grounds for eliminating a subarchitecture...
Quoted 7 lines
Well it's a question of whether we're likely to see increasing demand for it in the future. If so then it would be prudent to put some effort into fixing it up rather than removing it.
Seems that's not the case. I don't see a huge rush on this but if after this discussion nobody steps up to take care of the code over the next few weeks, it's best to remove it.
Perhaps a nicer way to do this is to add a compile warning or error:
#warning "
arch/i386/mach-pc9800unmaintained since xx/xx/xx, nominated for removal xx/xx/xx if unclaimed"
Quoted 7 lines
Quoted 4 lines
..where the second date is, say, 3+ months after the warning goes in. Then people can nominate stuff for removal with one liners and users will get ample opportunity to complain.
You're missing the point that this code doesn't compile *at all*. Nobody would ever see the warning.
Actually it's a matter of fail to attempt to compile, which is different than fail to compile. The principle is the same - stick advance notice in a highly visible place where users are likely to see it. That place is _not_ this mailing list.
We've had the code for years, and it would be nice to delete it if it's truly dead. But it seems silly to wake up one morning and say "no one's touched it for a year" and post a patch to delete it that same day. If it wasn't urgent yesterday, then why is it urgent today?
Signature · 1 line
Matt Mackall : http://www.selenic.com : Linux development and consulting
Quoted 9 lines · Matt Mackall
Actually it's a matter of fail to attempt to compile, which is different than fail to compile. The principle is the same - stick advance notice in a highly visible place where users are likely to see it. That place is _not_ this mailing list.
We've had the code for years, and it would be nice to delete it if it's truly dead. But it seems silly to wake up one morning and say "no one's touched it for a year" and post a patch to delete it that same day. If it wasn't urgent yesterday, then why is it urgent today?
I would agree if it were a complete feature, but it's not. PC9800 cannot be selected for compilation in the current kernel. Without an external patch set, it cannot be compiled or used. As far as I can tell, it's always been like that.
I think the best way of making someone sit up and take notice is simply to remove it. After all, given that we have the kernel under source control it's not like it's going to be hard to put it back if someone actually does notice and screams...
James