* Can support at Linux LXC?
@ 2015-11-20 21:46 Dererk
2015-11-21 12:33 ` Oliver Hartkopp
0 siblings, 1 reply; 3+ messages in thread
From: Dererk @ 2015-11-20 21:46 UTC (permalink / raw)
To: linux-can
Hi!
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?
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?
Thanks in advance!
Cheers,
Dererk
--
BOFH excuse #449:
greenpeace free'd the mallocs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Can support at Linux LXC?
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
0 siblings, 1 reply; 3+ messages in thread
From: Oliver Hartkopp @ 2015-11-21 12:33 UTC (permalink / raw)
To: Dererk, linux-can
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Can support at Linux LXC?
2015-11-21 12:33 ` Oliver Hartkopp
@ 2015-11-21 12:57 ` Oliver Hartkopp
0 siblings, 0 replies; 3+ messages in thread
From: Oliver Hartkopp @ 2015-11-21 12:57 UTC (permalink / raw)
To: Dererk, linux-can, Andri Yngvason
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-11-21 12:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.