New: Update configuration menu for MIPS target

https://bugs.busybox.net/show_bug.cgi?id=769

Host: Any
Target: MIPS/MIPSel
Summary: Update configuration menu for MIPS target
Product: buildroot
Version: 2009.11
Platform: Other
URL: http://morethan.org/bldrt/mips_arch.ods
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: minimod at morethan.org
ReportedBy: minimod at morethan.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0

The MIPS portion of the configuration menu is outdated and does not define the complete set of toolchain options for current cores.

At the above link, the following link and as an attachment is the table of information from which the additional configuration menu entries will be defined.

Table 1 shows the relationship between feature names and the instruction set.

Table 2 shows the relationship between core code names and features.

The actual configuration menu patch will follow any day, RSN.

http://morethan.org/bldrt/mips_arch.ods

Mikez

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Reviewed / Revised earlier version;
Added -march= options vs known cores table for gcc-2.95.3 through 4.5.dev. File at above link updated.

Yuck. I wonder why nobody tackled this mess before now? ;)

Not too surprising, not only are most of these machines being shipped with an Aug. 2005 kernel, a compiler is being used that is too old to provide code generation support specific to the core being used. Double yuck.

Mike

Now at revision 0.3, document at above link updated.

Having had my lessons in en_MIPS and en_GCC will now tackle the en_Kconfig language. ;)

Mike

Right! There is probably decades of history behind the answer.

Judging by the overwhelming number of comments on this project, it seems the active users of Buildroot for MIPS is down to just "self".

Where did I put my delete key?

Mike

Now at revision 0.4, document at above link updated. Various corrections and additions.
Documentation has caught up with, and passed gcc-4.5.dev.

Almost ready for my first en_Kconfig exam (change-set). RSN

Mike

Got the major part of the MIPS target configuration working; Broke everybody else's targets - S.H.

It isn't that bad, I wrote antemortem documentation about that, so I can fix them later.

Mike

https://bugs.busybox.net/show_bug.cgi?id=769

Mike Z <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |minimod at morethan.org

--- Comment #1 from Mike Z <[email protected]> 2009-12-13 18:46:19 UTC --- Screenshot of new MIPS target configuration sub-menu here:
http://morethan.org/bldrt/xconfig2.png

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Well, in spite of all the feedback I am getting on this project, I think it looks good. It also generates the required gcc options for cores from 1984 to October 2009.

Supports three modes:
"Full automatic" - based on Core codenames
"Semi-automatic" - Core codename + Manual modification of feature sets. "Full manual" - Baby, your on your own.

The real key to this project was the splitting of Config.in.arch into per-target files (Config.in.mips, Config.in.arm, ...).

That leaves each target arch to be dealt with by the lead contributor and/or target maintainer (12 people rather than 1) **without** any cross-target symbol dependencies (which Config.in.arch is full of).

Each target configuration sub-menu is "wrapped" with:
menu "MyArch target configuration"
depends on MyArch
- - - -
endmenu

Giving the closest thing to a namespace that kbuild understands.

The output interfaces with the existing Buildroot using the existing symbol names + plus target generated booleans to drive the CFLAGS option list generation.

Makes it much, much easier to add/remove/mark broken targets by arch.
Note: GCC supports 46 targets, **NO** I am not going to write 45 more of these things! Not even if someone paid me.

But getting the other current targets to continue working again is almost trivial - I planned it that way.

Mike

https://bugs.busybox.net/show_bug.cgi?id=769

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2009.11 |2010.05

--- Comment #2 from Thomas Petazzoni <[email protected]> 2010-02-21 22:33:05 UTC --- Move milestone to 2010.05 since enhancements will not be handled before the
release of 2010.02.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=769

Gustavo Zacarias <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #3 from Gustavo Zacarias <[email protected]> 2013-12-26 21:41:03 UTC --- Dead links plus revamping by mips developers over time supercedes this.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.