Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
Hi! > >>> Ok, plus there's already computing standard called "arc". > >>> > >>> https://www.linux-mips.org/wiki/ARC > >>> > >>> What about calling the architecture "sarc" or "syarc" ? > >> I think it would be best use of everybody's time if you could focus on > >> the technical content of the port rather than the name. It has been like > >> that for +10 years and I don't intend to make the kernel port name > >> different from THE arch name itself. > > Yeah, and it is best use of reviewers time to confuse them with > > one-letter difference to very popular architecture... and use three > > letter acronym that was already taken. > > > > In this state, I hope your port never gets merged. Yes, I got used to > > do cd a/ar. > > Although I really don't want to spend time arguing with you but still .. > if > you had a neighbor with same name as your friend your strategy most likely > would > be to force one of them to change names - kind of seems funny and > stupid. Yeah, imagine creating "/bin/mr" that would be du equivalent. How many people would delete their files by mistake? > Having said that, despite all the ranting so far, you've not managed to > comment on > a single line of the actual code, which is more funny and stupid. So Yeah, you tricked me into reviewing your code. No, I will not do more reviews for you. Yes, I bet I'm not the only one, and I bet that mistake will happen about once per developer. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Saturday 19 January 2013 01:16 AM, Pavel Machek wrote: > On Tue 2012-11-20 19:47:58, Vineet Gupta wrote: >> On Tuesday 20 November 2012 07:29 PM, Pavel Machek wrote: >>> On Tue 2012-11-20 14:47:37, Pavel Machek wrote: Hi! > > https://raw.github.com/vineetgarc/publish/master/ELCE-2012-ARC-Linux.pdf > > All comments/criticisms are welcome ! Huh. arch/arc is very similar to arch/arm. So similar that it took me 10 minutes to figure out. I guess theres no alternate name arc could use? >>> Hmm... "Advanced Risc"... :-(. >>> >>> Ok, plus there's already computing standard called "arc". >>> >>> https://www.linux-mips.org/wiki/ARC >>> >>> What about calling the architecture "sarc" or "syarc" ? >> I think it would be best use of everybody's time if you could focus on >> the technical content of the port rather than the name. It has been like >> that for +10 years and I don't intend to make the kernel port name >> different from THE arch name itself. > Yeah, and it is best use of reviewers time to confuse them with > one-letter difference to very popular architecture... and use three > letter acronym that was already taken. > > In this state, I hope your port never gets merged. Yes, I got used to > do cd a/ar. > Pavel Although I really don't want to spend time arguing with you but still .. if you had a neighbor with same name as your friend your strategy most likely would be to force one of them to change names - kind of seems funny and stupid. Having said that, despite all the ranting so far, you've not managed to comment on a single line of the actual code, which is more funny and stupid. So please stop blathering and do some constructive work. I won't go around asking ARC name to be changed because someone's Tab completion doesn't work anymore. And I'm sorry dude, that alone won't prevent the port from being merged. -Vineet -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
Hi! > > Yeah, and it is best use of reviewers time to confuse them with > > one-letter difference to very popular architecture... and use three > > letter acronym that was already taken. > > > > In this state, I hope your port never gets merged. Yes, I got used to > > do cd a/ar. > > You already lost that capability with the addition of arm64. As you > may remember, that one was proposed to be called arch/aarch64 at first, > which wasn't very popular ;-) Actually, with arm26, which is older IIRC. But tab still works there, just will not fill the last /, and you can't mistake arm64 with arm in filenames etc -- different length. > A lot of people are familiar with the ARC name, it's been around > for decades and has sold billions of CPUs under that name, likely > more than x86 or mips (still dwarfed by ARM of course). They've just Well, it seems that mips people were aware of the ARC name, it just meant something different: https://www.linux-mips.org/wiki/ARC Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Friday 18 January 2013, Pavel Machek wrote: > Yeah, and it is best use of reviewers time to confuse them with > one-letter difference to very popular architecture... and use three > letter acronym that was already taken. > > In this state, I hope your port never gets merged. Yes, I got used to > do cd a/ar. You already lost that capability with the addition of arm64. As you may remember, that one was proposed to be called arch/aarch64 at first, which wasn't very popular ;-) A lot of people are familiar with the ARC name, it's been around for decades and has sold billions of CPUs under that name, likely more than x86 or mips (still dwarfed by ARM of course). They've just kept a low profile so far and never tried to upstream their Linux port (unlike their gcc port, which was merged in 1997). I'm sure there are a lot of bad things one can say about Synopsys, but they are doing the right thing here, and calling their CPU architecture by a different name is not going to be helpful to their users. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Tue 2012-11-20 19:47:58, Vineet Gupta wrote: > On Tuesday 20 November 2012 07:29 PM, Pavel Machek wrote: > > On Tue 2012-11-20 14:47:37, Pavel Machek wrote: > >> Hi! > >> > >>> > >>> https://raw.github.com/vineetgarc/publish/master/ELCE-2012-ARC-Linux.pdf > >>> > >>> All comments/criticisms are welcome ! > >> Huh. arch/arc is very similar to arch/arm. So similar that it took me > >> 10 minutes to figure out. I guess theres no alternate name arc could > >> use? > > Hmm... "Advanced Risc"... :-(. > > > > Ok, plus there's already computing standard called "arc". > > > > https://www.linux-mips.org/wiki/ARC > > > > What about calling the architecture "sarc" or "syarc" ? > > I think it would be best use of everybody's time if you could focus on > the technical content of the port rather than the name. It has been like > that for +10 years and I don't intend to make the kernel port name > different from THE arch name itself. Yeah, and it is best use of reviewers time to confuse them with one-letter difference to very popular architecture... and use three letter acronym that was already taken. In this state, I hope your port never gets merged. Yes, I got used to do cd a/ar. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Tuesday 20 November 2012 07:29 PM, Pavel Machek wrote: > On Tue 2012-11-20 14:47:37, Pavel Machek wrote: >> Hi! >> >>> https://raw.github.com/vineetgarc/publish/master/ELCE-2012-ARC-Linux.pdf >>> >>> All comments/criticisms are welcome ! >> Huh. arch/arc is very similar to arch/arm. So similar that it took me >> 10 minutes to figure out. I guess theres no alternate name arc could >> use? > Hmm... "Advanced Risc"... :-(. > > Ok, plus there's already computing standard called "arc". > > https://www.linux-mips.org/wiki/ARC > > What about calling the architecture "sarc" or "syarc" ? I think it would be best use of everybody's time if you could focus on the technical content of the port rather than the name. It has been like that for +10 years and I don't intend to make the kernel port name different from THE arch name itself. > > Pavel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Tue 2012-11-20 14:47:37, Pavel Machek wrote: > Hi! > > > https://raw.github.com/vineetgarc/publish/master/ELCE-2012-ARC-Linux.pdf > > > > All comments/criticisms are welcome ! > > Huh. arch/arc is very similar to arch/arm. So similar that it took me > 10 minutes to figure out. I guess theres no alternate name arc could > use? Hmm... "Advanced Risc"... :-(. Ok, plus there's already computing standard called "arc". https://www.linux-mips.org/wiki/ARC What about calling the architecture "sarc" or "syarc" ? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Tuesday 20 November 2012 07:17 PM, Pavel Machek wrote: > Hi! > >> https://raw.github.com/vineetgarc/publish/master/ELCE-2012-ARC-Linux.pdf >> >> All comments/criticisms are welcome ! > Huh. arch/arc is very similar to arch/arm. So similar that it took me > 10 minutes to figure out. I guess theres no alternate name arc could > use? Thanks for the review comment - I'll pass this message to our marketing folks ! > > Pavel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
Hi! > https://raw.github.com/vineetgarc/publish/master/ELCE-2012-ARC-Linux.pdf > > All comments/criticisms are welcome ! Huh. arch/arc is very similar to arch/arm. So similar that it took me 10 minutes to figure out. I guess theres no alternate name arc could use? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
Hi Arnd, Thanks for your valuable comments I will rework the port. P.S. Sorry for top-posting. Thanks, Vineet On Wednesday 07 November 2012, Vineet Gupta wrote: > This patchset based off-of 3.7-rc3, introduces the Linux kernel port to > ARC700 processor family (750D and 770D) from Synopsys. > > ARC700 is highly configurable and power efficient 32-bit RISC core with MMU. > It is embedded in SoCs deployed in TV Set Top boxes, Digital Media Players, > all the way to Network-on-Chips. Hi Vineet, I'm largely quite happy with how the series has turned out, having looked at earlier versions of the ARC kernel a couple of years ago. I've commented already on individual patches, but overall, I see two main issues that need to be resolved in order to merge the port: * You have to use the generic syscall interface, and that means not using any of the legacy system calls that have since been replaced by newer versions of the same. * You are missing dynamic hardware detection. Rather than building a kernel with everything known about the hardware at compile time, new ports these days are normally able to run on all kinds of hardware and detect the differences by looking at configuration registers (e.g. PCI), asking firmware (Open Firmware, ACPI, ...) or by interpreting a device tree that is passed by the boot loader (most embedded systems). I assume that device tree is the right solution for you because a lot of the hardware you use is likely shared with ARM, PowerPC or MIPS based SoCs and they are all using (or getting migrated to) DT now instead of static platform devices, Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Wed, Nov 7, 2012 at 11:47 AM, Vineet Gupta wrote: > Hi, > > This patchset based off-of 3.7-rc3, introduces the Linux kernel port to > ARC700 processor family (750D and 770D) from Synopsys. We've been using the port for 6 month now at Ezchip running on top of FPGA in 4 way SMP configuration (support for which will no doubt follow later) and have subjected it to various stress tests (hackbench and such) and it is working up quite well over all. I realize some code style or organization changes might be in order but at the same time wanted to attest the nature of its good and behavior performance on real hardware; so for what it's worth: Tested-by: Gilad Ben-Yossef Cheers, Gilad -- Gilad Ben-Yossef Chief Coffee Drinker gi...@benyossef.com Israel Cell: +972-52-8260388 US Cell: +1-973-8260388 http://benyossef.com "If you take a class in large-scale robotics, can you end up in a situation where the homework eats your dog?" -- Jean-Baptiste Queru -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [RFC Patch v1 00/31] Synopsys ARC Linux kernel Port
On Wednesday 07 November 2012, Vineet Gupta wrote: > This patchset based off-of 3.7-rc3, introduces the Linux kernel port to > ARC700 processor family (750D and 770D) from Synopsys. > > ARC700 is highly configurable and power efficient 32-bit RISC core with MMU. > It is embedded in SoCs deployed in TV Set Top boxes, Digital Media Players, > all the way to Network-on-Chips. Hi Vineet, I'm largely quite happy with how the series has turned out, having looked at earlier versions of the ARC kernel a couple of years ago. I've commented already on individual patches, but overall, I see two main issues that need to be resolved in order to merge the port: * You have to use the generic syscall interface, and that means not using any of the legacy system calls that have since been replaced by newer versions of the same. * You are missing dynamic hardware detection. Rather than building a kernel with everything known about the hardware at compile time, new ports these days are normally able to run on all kinds of hardware and detect the differences by looking at configuration registers (e.g. PCI), asking firmware (Open Firmware, ACPI, ...) or by interpreting a device tree that is passed by the boot loader (most embedded systems). I assume that device tree is the right solution for you because a lot of the hardware you use is likely shared with ARM, PowerPC or MIPS based SoCs and they are all using (or getting migrated to) DT now instead of static platform devices, Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
