Linux CAN drivers development
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Dererk <dererk@debian.org>,
	linux-can@vger.kernel.org,
	Andri Yngvason <andri.yngvason@marel.com>
Subject: Re: Can support at Linux LXC?
Date: Sat, 21 Nov 2015 13:57:50 +0100	[thread overview]
Message-ID: <56506A4E.5010600@hartkopp.net> (raw)
In-Reply-To: <565064B1.7040502@hartkopp.net>

Hi Dererk,

just looked for more LXC information.

The Linux CAN subsystem is currently not aware of net namespaces.

We already had some discussions about it:
http://marc.info/?l=linux-can&w=2&r=1&s=namespace&q=b

but it did not get further from the last posting of Andri Yngvason as we all
seem not to be the name space specialists.

Regards,
Oliver


On 11/21/2015 01:33 PM, Oliver Hartkopp wrote:
> Hi Dererk,
> 
> On 11/20/2015 10:46 PM, Dererk wrote:
> 
>> I'm playing with some bus CANs and linux LXC. But it seems that there
>> must be some kind of support missing on the LXC side.
>> Even vcan seems to have the very same results on it when trying to open
>> the socket:
>>
>> socket(PF_CAN, SOCK_RAW, 1)             = -1 EAFNOSUPPORT (Address
>> family not supported by protocol)
>>
>> Have you have any experience with this?
> 
> Looks like CONFIG_CAN and other CAN specific components are not enabled in
> your kernel.
> 
> Debian kernels usually have this enabled:
> 
> $ grep CONFIG_CAN /boot/config-3.16.0-4-amd64
> CONFIG_CAN=m
> CONFIG_CAN_RAW=m
> CONFIG_CAN_BCM=m
> CONFIG_CAN_GW=m
> CONFIG_CAN_VCAN=m
> CONFIG_CAN_SLCAN=m
> CONFIG_CAN_DEV=m
> CONFIG_CAN_CALC_BITTIMING=y
> # CONFIG_CAN_LEDS is not set
> CONFIG_CAN_SJA1000=m
> CONFIG_CAN_SJA1000_ISA=m
> # CONFIG_CAN_SJA1000_PLATFORM is not set
> CONFIG_CAN_EMS_PCMCIA=m
> CONFIG_CAN_EMS_PCI=m
> CONFIG_CAN_PEAK_PCMCIA=m
> CONFIG_CAN_PEAK_PCI=m
> CONFIG_CAN_PEAK_PCIEC=y
> CONFIG_CAN_KVASER_PCI=m
> CONFIG_CAN_PLX_PCI=m
> # CONFIG_CAN_C_CAN is not set
> # CONFIG_CAN_CC770 is not set
> # CONFIG_CAN_MCP251X is not set
> CONFIG_CAN_EMS_USB=m
> CONFIG_CAN_ESD_USB2=m
> CONFIG_CAN_GS_USB=m
> CONFIG_CAN_KVASER_USB=m
> CONFIG_CAN_PEAK_USB=m
> CONFIG_CAN_8DEV_USB=m
> CONFIG_CAN_SOFTING=m
> CONFIG_CAN_SOFTING_CS=m
> # CONFIG_CAN_DEBUG_DEVICES is not set
> 
> 
>> Is there a proper place where I could route this doubts at an
>> specialized mailing list on the linux kernel that you know might be more
>> appropiate?
> 
> You are definitely at the right place for CAN related questions here :-)
> 
> Best regards,
> Oliver
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2015-11-21 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 21:46 Can support at Linux LXC? Dererk
2015-11-21 12:33 ` Oliver Hartkopp
2015-11-21 12:57   ` Oliver Hartkopp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56506A4E.5010600@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=andri.yngvason@marel.com \
    --cc=dererk@debian.org \
    --cc=linux-can@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox