Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755505Ab1BNEx7 (ORCPT ); Sun, 13 Feb 2011 23:53:59 -0500 Received: from mail-yx0-f174.google.com ([209.85.213.174]:37407 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751094Ab1BNEx5 (ORCPT ); Sun, 13 Feb 2011 23:53:57 -0500 Message-ID: From: "Subhasish Ghosh" To: "Kurt Van Dijck" Cc: , , , , , "Wolfgang Grandegger" , "open list:CAN NETWORK DRIVERS" , "open list:CAN NETWORK DRIVERS" , "open list" References: <1297435892-28278-1-git-send-email-subhasish@mistralsolutions.com> <1297435892-28278-10-git-send-email-subhasish@mistralsolutions.com> <20110211150602.GB373@e-circ.dyndns.org> In-Reply-To: <20110211150602.GB373@e-circ.dyndns.org> Subject: Re: [PATCH v2 09/13] can: pruss CAN driver. Date: Mon, 14 Feb 2011 10:24:48 +0530 Organization: Mistral Solutions MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3142 Lines: 95 Hello, I had a discussion regarding this with Wolfgang: http://www.mail-archive.com/socketcan-users@lists.berlios.de/msg00324.html The problem here is that we must configure the mailbox ID's and this support is not available in the socketCan sub-system. -------------------------------------------------- From: "Kurt Van Dijck" Sent: Friday, February 11, 2011 8:36 PM To: "Subhasish Ghosh" Cc: ; ; ; ; ; "Wolfgang Grandegger" ; "open list:CAN NETWORK DRIVERS" ; "open list:CAN NETWORK DRIVERS" ; "open list" Subject: Re: [PATCH v2 09/13] can: pruss CAN driver. > On Fri, Feb 11, 2011 at 08:21:28PM +0530, Subhasish Ghosh wrote: >> +config DA8XX_PRU_CANID_MBX0 >> + hex "CANID for mailbox 0" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 0 >> + Default value is set to 0x123, change this as required. >> + >> +config DA8XX_PRU_CANID_MBX1 >> + hex "CANID for mailbox 1" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 1 >> + Default value is set to 0x123, change this as required. >> + >> +config DA8XX_PRU_CANID_MBX2 >> + hex "CANID for mailbox 2" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 2 >> + Default value is set to 0x123, change this as required. >> + >> +config DA8XX_PRU_CANID_MBX3 >> + hex "CANID for mailbox 3" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 3 >> + Default value is set to 0x123, change this as required. >> + >> +config DA8XX_PRU_CANID_MBX4 >> + hex "CANID for mailbox 4" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 4 >> + Default value is set to 0x123, change this as required. >> + >> +config DA8XX_PRU_CANID_MBX5 >> + hex "CANID for mailbox 5" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 5 >> + Default value is set to 0x123, change this as required. >> + >> +config DA8XX_PRU_CANID_MBX6 >> + hex "CANID for mailbox 6" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 6 >> + Default value is set to 0x123, change this as required. >> + >> +config DA8XX_PRU_CANID_MBX7 >> + hex "CANID for mailbox 7" >> + depends on CAN_TI_DA8XX_PRU >> + default "0x123" >> + ---help--- >> + Enter the CANID for mailbox 7 >> + Default value is set to 0x123, change this as required. > Why is filling the mailboxes the job of kernel config? > > Regards, > Kurt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/