Re: RFC: Remove the arm26 port
On Sun, 2007-07-29 at 13:50 +0200, Adrian Bunk wrote: > Considering the state of the arm26 port, I do hereby suggest to remove > it from the Linx kernel since it's far from a usable state and doesn't > seem to come back into a usable state. > > If anyone wants to work on getting this port back into a usable state in > the forseeable future he should speak up now. Hi guys. Obviously I havent had time to work on the port in some time now - I am ok with it being dropped - the work of splitting it out wont be lost and until its fixed up, its just in other peoples way. If I get time to work on it in future, I'll let you all know. -Ian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RFC: Remove the arm26 port
* Adrian Bunk ([EMAIL PROTECTED]) wrote: > Considering the state of the arm26 port, I do hereby suggest to remove > it from the Linx kernel since it's far from a usable state and doesn't > seem to come back into a usable state. > > If anyone wants to work on getting this port back into a usable state in > the forseeable future he should speak up now. As was being discussed a few weeks ago; the drivers/acorn/block should go at the same time since they are only in ARM 26 machines. Dave -- -Open up your eyes, open up your mind, open up your code --- / Dr. David Alan Gilbert| Running GNU/Linux on Alpha,68K| Happy \ \ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex / \ _|_ http://www.treblig.org |___/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RFC: Remove the arm26 port
On Sun, Jul 29, 2007 at 01:10:12PM +0100, Christoph Hellwig wrote: > On Sun, Jul 29, 2007 at 01:50:40PM +0200, Adrian Bunk wrote: > > Considering the state of the arm26 port, I do hereby suggest to remove > > it from the Linx kernel since it's far from a usable state and doesn't > > seem to come back into a usable state. > > > > If anyone wants to work on getting this port back into a usable state in > > the forseeable future he should speak up now. > > Yes, please. This bitrotting code has been in the way for quite bit of > cross-architecture work I've been doing. > > Btw, there's probably no point to Cc rmk as he's not involved with that > stinkin' pile. Definitely - I'd like to see it gone so hopefully I'll stop being copied on every single janitorial change to it. (And yes, I've re-enabled mail-followup-to since otherwise I can't group-reply in mutt to everyone - without it I just get hch in the To: header and an empty CC: with 'g'. Tough shit to those anti-mail-followup-to people. It's the only thing that actually works.) -- Russell King Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RFC: Remove the arm26 port
On Sun, Jul 29, 2007 at 01:50:40PM +0200, Adrian Bunk wrote: > Considering the state of the arm26 port, I do hereby suggest to remove > it from the Linx kernel since it's far from a usable state and doesn't > seem to come back into a usable state. > > If anyone wants to work on getting this port back into a usable state in > the forseeable future he should speak up now. Yes, please. This bitrotting code has been in the way for quite bit of cross-architecture work I've been doing. Btw, there's probably no point to Cc rmk as he's not involved with that stinkin' pile. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RFC: Remove the arm26 port
Considering the state of the arm26 port, I do hereby suggest to remove it from the Linx kernel since it's far from a usable state and doesn't seem to come back into a usable state. If anyone wants to work on getting this port back into a usable state in the forseeable future he should speak up now. cu Adrian On Sat, Jul 07, 2007 at 10:12:08PM +0200, Adrian Bunk wrote: > I'm wondering what the status of the arm26 port in the kernel is: > > AFAIR gcc support for this architecture was deprecated in gcc 3.4 and > removed in gcc 4.0. This implies that either someone will have to re-add > support to gcc in the next 1-2 years or the kernel port will become > useless with the next increase of the minimum gcc requirement for the > kernel. > > The other point is that I tried to cross-compile an arm26 defconfig. > I gave up after running into several compile errors, and it doesn't seem > as if any recent kernel could be compiled. > > Is the arm26 kernel port already unused dead code or is some work for > getting it back into shape pending? > > cu > Adrian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RFC: Remove the arm26 port
Considering the state of the arm26 port, I do hereby suggest to remove it from the Linx kernel since it's far from a usable state and doesn't seem to come back into a usable state. If anyone wants to work on getting this port back into a usable state in the forseeable future he should speak up now. cu Adrian On Sat, Jul 07, 2007 at 10:12:08PM +0200, Adrian Bunk wrote: I'm wondering what the status of the arm26 port in the kernel is: AFAIR gcc support for this architecture was deprecated in gcc 3.4 and removed in gcc 4.0. This implies that either someone will have to re-add support to gcc in the next 1-2 years or the kernel port will become useless with the next increase of the minimum gcc requirement for the kernel. The other point is that I tried to cross-compile an arm26 defconfig. I gave up after running into several compile errors, and it doesn't seem as if any recent kernel could be compiled. Is the arm26 kernel port already unused dead code or is some work for getting it back into shape pending? cu Adrian - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RFC: Remove the arm26 port
On Sun, Jul 29, 2007 at 01:50:40PM +0200, Adrian Bunk wrote: Considering the state of the arm26 port, I do hereby suggest to remove it from the Linx kernel since it's far from a usable state and doesn't seem to come back into a usable state. If anyone wants to work on getting this port back into a usable state in the forseeable future he should speak up now. Yes, please. This bitrotting code has been in the way for quite bit of cross-architecture work I've been doing. Btw, there's probably no point to Cc rmk as he's not involved with that stinkin' pile. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RFC: Remove the arm26 port
On Sun, Jul 29, 2007 at 01:10:12PM +0100, Christoph Hellwig wrote: On Sun, Jul 29, 2007 at 01:50:40PM +0200, Adrian Bunk wrote: Considering the state of the arm26 port, I do hereby suggest to remove it from the Linx kernel since it's far from a usable state and doesn't seem to come back into a usable state. If anyone wants to work on getting this port back into a usable state in the forseeable future he should speak up now. Yes, please. This bitrotting code has been in the way for quite bit of cross-architecture work I've been doing. Btw, there's probably no point to Cc rmk as he's not involved with that stinkin' pile. Definitely - I'd like to see it gone so hopefully I'll stop being copied on every single janitorial change to it. (And yes, I've re-enabled mail-followup-to since otherwise I can't group-reply in mutt to everyone - without it I just get hch in the To: header and an empty CC: with 'g'. Tough shit to those anti-mail-followup-to people. It's the only thing that actually works.) -- Russell King Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RFC: Remove the arm26 port
* Adrian Bunk ([EMAIL PROTECTED]) wrote: Considering the state of the arm26 port, I do hereby suggest to remove it from the Linx kernel since it's far from a usable state and doesn't seem to come back into a usable state. If anyone wants to work on getting this port back into a usable state in the forseeable future he should speak up now. As was being discussed a few weeks ago; the drivers/acorn/block should go at the same time since they are only in ARM 26 machines. Dave -- -Open up your eyes, open up your mind, open up your code --- / Dr. David Alan Gilbert| Running GNU/Linux on Alpha,68K| Happy \ \ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC HPPA | In Hex / \ _|_ http://www.treblig.org |___/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: RFC: Remove the arm26 port
On Sun, 2007-07-29 at 13:50 +0200, Adrian Bunk wrote: Considering the state of the arm26 port, I do hereby suggest to remove it from the Linx kernel since it's far from a usable state and doesn't seem to come back into a usable state. If anyone wants to work on getting this port back into a usable state in the forseeable future he should speak up now. Hi guys. Obviously I havent had time to work on the port in some time now - I am ok with it being dropped - the work of splitting it out wont be lost and until its fixed up, its just in other peoples way. If I get time to work on it in future, I'll let you all know. -Ian - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
