Bug 68811

Summary: [POWERPC] pasemi: Nemo support
Product: Platform Specific/Hardware Reporter: Christian Zigotzky (chzigotzky)
Component: PPC-64Assignee: Anton Blanchard (anton)
Status: RESOLVED INVALID    
Severity: normal CC: chzigotzky, olof
Priority: P1    
Hardware: PPC-64   
OS: Linux   
Kernel Version: 3.1X Subsystem:
Regression: No Bisected commit-id:
Attachments: nemo patch

Description Christian Zigotzky 2014-01-16 13:28:54 UTC 
Created attachment 122261 [details]
nemo patch

Hi All,

We have created a patch to support the A-EON Nemo board. Nemo uses the AMD/ATI SB600 South Bridge to provide various integrated I/O functions including
SATA/PATA ports, USB and audio. The SB600’s HD Audio controller is connected to an IDT 92HD700 codec. This patch makes the kernel compatible with the SB600 chipset and the HD Audio chip on the Nemo board. It also solved any problems with Radeon HD graphics cards. Is it possible to integrate this patch to the official kernel sources?

Information about the Nemo board:

CPU: PA Semi Dual-core PA6T-1682M, nominal 2.0GHz (1.8GHz standard) PowerISA™ v2.04+
4x DDR2 RAM slots
10x USB 2.0
1x Gigabit Ethernet
2x PCIe x16 slots (1x16 or 2x8)
2x PCIe x1 slots
1x Xorro slot
2x PCI legacy slots
2x RS232
4x SATA 2 connectors
1x IDE connector
JTAG connector
1x Compact Flash
1x "Xena" 500MHz XMOS XS1-L2 124

http://en.wikipedia.org/wiki/AmigaOne_X1000
http://www.a-eon.com/?page=nemo
http://www.supertuxkart-amiga.de/amiga/x1000.html

Rgds,
Christian
Comment 1 Olof Johansson 2014-01-16 22:37:20 UTC 
This is now how you submit code to be included in the kernel. Please read Documentation/SubmittingPatches.

The code needs to be split up into separate patches, one patch per change, one change per patch. Read the above doc for info on how to prepare your code.

It also violates coding standards and it seems to possibly break multiplatform kernel (i.e. if you enable nemo support, other platforms will not work as well any more).

Marking this bug resolved.
Comment 2 Alan 2014-01-16 22:38:32 UTC 
Yes.

See Documentation/SubmittingPatches

there is a process for patch submission so we can reliably trace origin/rights.

The patch as presented will want splitting into different items, and cleaning up (eg you've got debugging stuff still hacked into it) but that is somethign you can work with the PPC tree maintainers to resolve.

I would start with the PPC related lists/maintainers