* Adding support for new BSP
@ 2004-05-14 17:06 Tiwari, Rakesh
2004-05-14 17:32 ` Ralf Baechle
0 siblings, 1 reply; 4+ messages in thread
From: Tiwari, Rakesh @ 2004-05-14 17:06 UTC (permalink / raw)
To: linux-mips; +Cc: 'Ralf Baechle'
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
Hi,
We plan to add our (IDT) BSP (board support package) for evaluation boards
based on IDT 32 bit MIPS processors to the main mips-linux 2.6.x kernel.
Can somebody please tell me the procedure/requirements to check-in the new
BSP files into the main kernel tree.
Any suggestions/pointers would be appreciated.
Thanks
Rakesh
[-- Attachment #2: Type: text/html, Size: 957 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Adding support for new BSP
2004-05-14 17:06 Adding support for new BSP Tiwari, Rakesh
@ 2004-05-14 17:32 ` Ralf Baechle
2004-05-14 17:35 ` Pete Popov
0 siblings, 1 reply; 4+ messages in thread
From: Ralf Baechle @ 2004-05-14 17:32 UTC (permalink / raw)
To: Tiwari, Rakesh; +Cc: linux-mips
On Fri, May 14, 2004 at 10:06:16AM -0700, Tiwari, Rakesh wrote:
> We plan to add our (IDT) BSP (board support package) for evaluation boards
> based on IDT 32 bit MIPS processors to the main mips-linux 2.6.x kernel.
>
> Can somebody please tell me the procedure/requirements to check-in the new
> BSP files into the main kernel tree.
Send me a patch; cc'ing linux-mips can't harm. I'll either apply or
comment the patch.
Ralf
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Adding support for new BSP
2004-05-14 17:32 ` Ralf Baechle
@ 2004-05-14 17:35 ` Pete Popov
0 siblings, 0 replies; 4+ messages in thread
From: Pete Popov @ 2004-05-14 17:35 UTC (permalink / raw)
To: Tiwari, Rakesh; +Cc: Ralf Baechle, linux-mips
Ralf Baechle wrote:
>On Fri, May 14, 2004 at 10:06:16AM -0700, Tiwari, Rakesh wrote:
>
>
>
>>We plan to add our (IDT) BSP (board support package) for evaluation boards
>>based on IDT 32 bit MIPS processors to the main mips-linux 2.6.x kernel.
>>
>>Can somebody please tell me the procedure/requirements to check-in the new
>>BSP files into the main kernel tree.
>>
>>
>
>Send me a patch; cc'ing linux-mips can't harm. I'll either apply or
>comment the patch.
>
>
Take a look at the CodingStyle doc in the Documentation directory first.
That will save you and Ralf sometime.
Pete
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Adding support for new BSP
@ 2004-05-14 20:49 Tiwari, Rakesh
0 siblings, 0 replies; 4+ messages in thread
From: Tiwari, Rakesh @ 2004-05-14 20:49 UTC (permalink / raw)
To: 'Pete Popov', Tiwari, Rakesh; +Cc: Ralf Baechle, linux-mips
Thanks Ralf and Pete.
I will check for the Coding Style compliance and mail you the
patch sometime next week.
Thanks
Rakesh
-----Original Message-----
From: Pete Popov [mailto:ppopov@mvista.com]
Sent: Friday, May 14, 2004 10:36 AM
To: Tiwari, Rakesh
Cc: Ralf Baechle; linux-mips@linux-mips.org
Subject: Re: Adding support for new BSP
Ralf Baechle wrote:
>On Fri, May 14, 2004 at 10:06:16AM -0700, Tiwari, Rakesh wrote:
>
>
>
>>We plan to add our (IDT) BSP (board support package) for evaluation
>>boards based on IDT 32 bit MIPS processors to the main mips-linux
>>2.6.x kernel.
>>
>>Can somebody please tell me the procedure/requirements to check-in the
>>new BSP files into the main kernel tree.
>>
>>
>
>Send me a patch; cc'ing linux-mips can't harm. I'll either apply or
>comment the patch.
>
>
Take a look at the CodingStyle doc in the Documentation directory first.
That will save you and Ralf sometime.
Pete
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-05-14 20:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-14 17:06 Adding support for new BSP Tiwari, Rakesh
2004-05-14 17:32 ` Ralf Baechle
2004-05-14 17:35 ` Pete Popov
-- strict thread matches above, loose matches on Subject: below --
2004-05-14 20:49 Tiwari, Rakesh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox