From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BBD846BB52 for ; Wed, 21 Feb 2024 13:17:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708521423; cv=none; b=FWMgiAZhn9m/Id21PoSCKvLiVNf7wZqrPIf5mhQhSei+j8tGkcm5/ZpACNErYgSaoBjOiWgaG7OVijR4wAejDg215FZDkAti5fZDEKM2whCWqs2RLdQyiiU+SOZfDkMxkHEe2k/47R27bvSqR9Q4cT3PzuDRuSWw0lBusxFczKU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708521423; c=relaxed/simple; bh=Zy49exQngjBnqtJm9LbsD/Y7AaCQipJaILR8EsS+9y4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ESMMBAT8uzrIliis79iqB1DhkQZ3+1PVvlFpeWAkwACq8uVPKgSdhf6wLl5P0Fy3hWPuei+JEhwCcVTwciCkZopBUyTHmGkyvag0n65OwfUnMZw/GF3F8nZJd4a2i9IIcibV0h3Vs3VyOFwY6uxEN7AZTRvVgTiH5zWVPEPVlZI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=ZExeCK6x; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="ZExeCK6x" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1708521420; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=m/w1WDwOHGakhJUAR/C6JZj5tsVNs/vIQZ9PZvXihR0=; b=ZExeCK6xk3w6UjWhSajjUShW7yIJyFzmdMnri7cqbqlYQ2pt76EnfHRQ37qi8r7goscbg6 6Jq4fkXZmpNNc/o5cZfYLb3T1ZD4go2P3dwf52oXp3ZC2QaFc2+N75FN5sryXowgW+o/AK N3Q3GBfjAvZOVYMV0Sbd0e/VxCyWS60= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-215-COc188c8MRWvZvrvLL475Q-1; Wed, 21 Feb 2024 08:16:58 -0500 X-MC-Unique: COc188c8MRWvZvrvLL475Q-1 Received: by mail-lj1-f197.google.com with SMTP id 38308e7fff4ca-2d256d36f6bso5158601fa.0 for ; Wed, 21 Feb 2024 05:16:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708521417; x=1709126217; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=m/w1WDwOHGakhJUAR/C6JZj5tsVNs/vIQZ9PZvXihR0=; b=Ot9uJonHiaYqlGvuIJFvbKudjNu6w0DRFDVc16+pqyBpfPGMhV1tVbGjSg4S+N9S2E LML1mw7FSPZZpw1H8SB1bazOVFeJEmqwdQktmcHlKhLf1ph9B0Xfj5S+lNqURGu1G9DJ H0ziYPs3kl69N6yy7OSuO1aRMuKdrZCdBbxcHOvJ7jxlaIdf0i8jlfFkRce9ERTfLMWf 80y+GDV63NwSdGUCTX9okJZixQURoOsrhbGIR+7v+LpgYeEVqxPMAPcI3US3cVijKAdX mnseh667QQq6VVPH6zOd3vIIzdO3K5N8mT2bKhNWXkL8uIPu0UUdo4mhVdR8OLT7lUFN 2GJg== X-Forwarded-Encrypted: i=1; AJvYcCUaulGto5ZCXY7dJSX/Dm29SWeLRJ50gkVHpMFcttKpfclLawiWdKpm3NxGnqG4sNJNzomD6Pje1Y/M2OjQeF1c3560h/Esf6Hq X-Gm-Message-State: AOJu0Yz5eiQDraMnzBo7cMlgFz5sPX5/lKpSsdF0AWnjVea+Xmlk5hXw XW/q0sFZjf/Pa7eoL2XvRYHCBWrb/rOks924MCJdywvbdGxx/93VX2vzj2fegYFoIJg9kGBuvH0 kk8vNMo8quna0oPYeddULwkHCa8XPqLc8ZXkpj/NMM4WZIykRJdrGPY7Ju8I4tQdSSQ== X-Received: by 2002:a2e:9858:0:b0:2d2:31f4:35c with SMTP id e24-20020a2e9858000000b002d231f4035cmr6596916ljj.25.1708521417005; Wed, 21 Feb 2024 05:16:57 -0800 (PST) X-Google-Smtp-Source: AGHT+IGqTrtmtAQXm6a084V0K36E+nFmsfirlA7sHCUWcc7J24nFFUapF0/gtS/pp7AUV6Fb2PWRSQ== X-Received: by 2002:a2e:9858:0:b0:2d2:31f4:35c with SMTP id e24-20020a2e9858000000b002d231f4035cmr6596894ljj.25.1708521416595; Wed, 21 Feb 2024 05:16:56 -0800 (PST) Received: from fedora ([2a01:e0a:257:8c60:80f1:cdf8:48d0:b0a1]) by smtp.gmail.com with ESMTPSA id f7-20020a5d5687000000b0033ce727e728sm16677525wrv.94.2024.02.21.05.16.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Feb 2024 05:16:56 -0800 (PST) Date: Wed, 21 Feb 2024 14:16:54 +0100 From: Matias Ezequiel Vara Larsen To: Marc Kleine-Budde Cc: Mikhail Golubev-Ciuchea , virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org, Harald Mommer Subject: Re: [virtio-dev] Re: [virtio-comment] [RFC PATCH v3] virtio-can: Device specification. Message-ID: References: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> <20240221-acts-decade-76d3d69e8e4d-mkl@pengutronix.de> Precedence: bulk X-Mailing-List: linux-can@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240221-acts-decade-76d3d69e8e4d-mkl@pengutronix.de> On Wed, Feb 21, 2024 at 01:49:31PM +0100, Marc Kleine-Budde wrote: > On 21.02.2024 11:37:58, Matias Ezequiel Vara Larsen wrote: > > > > +The length of the \field{sdu} is determined by the \field{length}. > > > > + > > > > +The type of a CAN message identifier is determined by \field{flags}. The > > > > +3 most significant bits of \field{can_id} do not bear the information > > > > +about the type of the CAN message identifier and are 0. > > > > + > > > > +The device MUST reject any CAN frame type for which support has not been > > > > +negotiated with VIRTIO_CAN_RESULT_NOT_OK in \field{result} and MUST NOT > > > > +schedule the message for transmission. A CAN frame with an undefined bit > > > > +set in \field{flags} is treated like a CAN frame for which support has > > > > +not been negotiated. > > > > + > > > > +The device MUST reject any CAN frame for which \field{can_id} or > > > > +\field{sdu} length are out of range or the CAN controller is in an > > > > +invalid state with VIRTIO_CAN_RESULT_NOT_OK in \field{result} and MUST > > > > +NOT schedule the message for transmission. > > > > + > > I am not very familiar with CAN but how does the device figure out that > > the can_id is out of range? > > In classical CAN we have the standard CAN frames, which have an 11 bit > ID, and there are extended CAN frames, which have 29 bits ID. Extended > frames are signaled with VIRTIO_CAN_FLAGS_EXTENDED set. > > So if a standard frame uses more than 11 Bits of CAN-ID, it's considered > out of range. > Thanks Marc for the explanation. Do you think that it would be worthwhile to add that to the spec at some point? Matias. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DABE2C48BF6 for ; Wed, 21 Feb 2024 13:17:03 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id 1E2F32B014 for ; Wed, 21 Feb 2024 13:17:03 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 00BDB986538 for ; Wed, 21 Feb 2024 13:17:02 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id D4F1C9864A1; Wed, 21 Feb 2024 13:17:02 +0000 (UTC) Mailing-List: contact virtio-comment-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id C4AA89864B2 for ; Wed, 21 Feb 2024 13:17:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: 8TLjal75NrqwXFGXldlEJA-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708521417; x=1709126217; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=m/w1WDwOHGakhJUAR/C6JZj5tsVNs/vIQZ9PZvXihR0=; b=EgZxkcfURGeRnQK0wSHiVG/E80eRl01/Raq6sxxQ6Cx/cFWkxsPtnZhSQ4M97mvuRp Ih5F2pv9/9ro90Mkr4VCmfKHo0jIdg4GcxW2QFbREBpgC4iZ94mdcxxpSEwPAvJNml48 LtQZOJTERyOafJtv3RoC7atYL1rWIRMhcVgvZfYcazhji1YqjmSJZdlLE4lZlQVhHcjR FRfSg/89wOr/8Ol+W8Xfp/3GLcB0pm0cNXi2iO0st9Trb14Tz9VOcz8hywWh0LJS+PAL mhw0+AGlz1vuDxZUjhxR4MhOG1pKqMBBnNMGo9ndD9OlZW0vSrIp5kB/KwJqfvALrzTE Ecsw== X-Forwarded-Encrypted: i=1; AJvYcCVDR56e3041AGpBZM7sOpiT03HDv0vphzr/KYoNNkcbs1bkuNWzV8Xwgn2ZXqocsuAcU7EOTKQWD5xho/HcFjKeYuOtj+BHWaGRwZgSG3qi9brGTQ== X-Gm-Message-State: AOJu0Yys0JAfqVnPQJVOOqriFjeePgSsvIwcvrUuRxXQ/pZac/doZStN i5WF4i0f1v1wKqePS1ujSQ0jVFeQapqlzU84xi0XgV4B2hl+Gm32QP8IXFtuE1ZVV6AojtgO6ve 4RAQl4OkW+i7TKVCy0LMvW8/pMfno1QuaVa0kVufY+7d3ItjlxpAcOpKB0toVoXQiwVzWrVU= X-Received: by 2002:a2e:9858:0:b0:2d2:31f4:35c with SMTP id e24-20020a2e9858000000b002d231f4035cmr6596915ljj.25.1708521417002; Wed, 21 Feb 2024 05:16:57 -0800 (PST) X-Google-Smtp-Source: AGHT+IGqTrtmtAQXm6a084V0K36E+nFmsfirlA7sHCUWcc7J24nFFUapF0/gtS/pp7AUV6Fb2PWRSQ== X-Received: by 2002:a2e:9858:0:b0:2d2:31f4:35c with SMTP id e24-20020a2e9858000000b002d231f4035cmr6596894ljj.25.1708521416595; Wed, 21 Feb 2024 05:16:56 -0800 (PST) Date: Wed, 21 Feb 2024 14:16:54 +0100 From: Matias Ezequiel Vara Larsen To: Marc Kleine-Budde Cc: Mikhail Golubev-Ciuchea , virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org, Harald Mommer Message-ID: References: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> <20240221-acts-decade-76d3d69e8e4d-mkl@pengutronix.de> MIME-Version: 1.0 In-Reply-To: <20240221-acts-decade-76d3d69e8e4d-mkl@pengutronix.de> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [virtio-comment] Re: [virtio-dev] Re: [virtio-comment] [RFC PATCH v3] virtio-can: Device specification. On Wed, Feb 21, 2024 at 01:49:31PM +0100, Marc Kleine-Budde wrote: > On 21.02.2024 11:37:58, Matias Ezequiel Vara Larsen wrote: > > > > +The length of the \field{sdu} is determined by the \field{length}. > > > > + > > > > +The type of a CAN message identifier is determined by \field{flags}. The > > > > +3 most significant bits of \field{can_id} do not bear the information > > > > +about the type of the CAN message identifier and are 0. > > > > + > > > > +The device MUST reject any CAN frame type for which support has not been > > > > +negotiated with VIRTIO_CAN_RESULT_NOT_OK in \field{result} and MUST NOT > > > > +schedule the message for transmission. A CAN frame with an undefined bit > > > > +set in \field{flags} is treated like a CAN frame for which support has > > > > +not been negotiated. > > > > + > > > > +The device MUST reject any CAN frame for which \field{can_id} or > > > > +\field{sdu} length are out of range or the CAN controller is in an > > > > +invalid state with VIRTIO_CAN_RESULT_NOT_OK in \field{result} and MUST > > > > +NOT schedule the message for transmission. > > > > + > > I am not very familiar with CAN but how does the device figure out that > > the can_id is out of range? > > In classical CAN we have the standard CAN frames, which have an 11 bit > ID, and there are extended CAN frames, which have 29 bits ID. Extended > frames are signaled with VIRTIO_CAN_FLAGS_EXTENDED set. > > So if a standard frame uses more than 11 Bits of CAN-ID, it's considered > out of range. > Thanks Marc for the explanation. Do you think that it would be worthwhile to add that to the spec at some point? Matias. This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CA4E3C48BC3 for ; Wed, 21 Feb 2024 13:17:05 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id 2C1732AC9B for ; Wed, 21 Feb 2024 13:17:05 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 236D798654C for ; Wed, 21 Feb 2024 13:17:05 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id 11E7C9864F2; Wed, 21 Feb 2024 13:17:05 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 0220A9864B0 for ; Wed, 21 Feb 2024 13:17:04 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: Nmlsrk4GMxG5ae6AIk3oIg-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708521417; x=1709126217; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=m/w1WDwOHGakhJUAR/C6JZj5tsVNs/vIQZ9PZvXihR0=; b=sfaVtXQbhB7MbUHHj41UvQdrDnewOYyBChsYrjq+zzEjhyiLtpnfCA59LNzlVujF/J uLz1jIKfk3dZ4KXfmwfoEHuPQSGQfCgAb0a0sThW99ZP+b5GJ1emBUA+U0GuXjLDySs7 rFEZHX74umo3DGJbAu66dcEJAEgLO+o4P7MBqL5to0KVAo7PJ07TTJ3Ae3z6TWUruYNQ 7ZPB7SY3KW9lB1tZLaBUePhm8ePOoqSN5rqOZrhJ0cROgU8luhZzntTderE6BtJ8trPD xeG/teIRSyxmUP0koAuhTgnojygKDfST7xVcba1N8uP3Ie4Hny/VzTpEefNSQPu68cJO D8yQ== X-Forwarded-Encrypted: i=1; AJvYcCW7pfMshA/bTPWr4AWpiOYrVl6mToiAAKpZXg5lDFwr1iq7vP/4ueh1M9uqGAJ+hDhtehS10xytOfjJNDiq6Zt9RbUSSAsH9oSWWmr9q0cm X-Gm-Message-State: AOJu0YxWeFatcJBPVsThNjjEe+vMtdF2gnq4pep4pB2/GonsCZV7pJvb 0SyVWDJd8NO3XrkqlF0f1bnv9tr80Z1ufNJ2rVSRR/y2+E1bg1x1/8gKzWU6WaJxdehJ1o9Tsot vGGUONMnqgJGlfiYuskhTxsU5nMp/EtwqsqBCAQHMlhYas0DDkChFaYcsaC/DrFr0OA== X-Received: by 2002:a2e:9858:0:b0:2d2:31f4:35c with SMTP id e24-20020a2e9858000000b002d231f4035cmr6596914ljj.25.1708521417002; Wed, 21 Feb 2024 05:16:57 -0800 (PST) X-Google-Smtp-Source: AGHT+IGqTrtmtAQXm6a084V0K36E+nFmsfirlA7sHCUWcc7J24nFFUapF0/gtS/pp7AUV6Fb2PWRSQ== X-Received: by 2002:a2e:9858:0:b0:2d2:31f4:35c with SMTP id e24-20020a2e9858000000b002d231f4035cmr6596894ljj.25.1708521416595; Wed, 21 Feb 2024 05:16:56 -0800 (PST) Date: Wed, 21 Feb 2024 14:16:54 +0100 From: Matias Ezequiel Vara Larsen To: Marc Kleine-Budde Cc: Mikhail Golubev-Ciuchea , virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org, Harald Mommer Message-ID: References: <20230609142243.199074-1-Mikhail.Golubev-Ciuchea@opensynergy.com> <20240221-acts-decade-76d3d69e8e4d-mkl@pengutronix.de> MIME-Version: 1.0 In-Reply-To: <20240221-acts-decade-76d3d69e8e4d-mkl@pengutronix.de> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: [virtio-dev] Re: [virtio-comment] [RFC PATCH v3] virtio-can: Device specification. On Wed, Feb 21, 2024 at 01:49:31PM +0100, Marc Kleine-Budde wrote: > On 21.02.2024 11:37:58, Matias Ezequiel Vara Larsen wrote: > > > > +The length of the \field{sdu} is determined by the \field{length}. > > > > + > > > > +The type of a CAN message identifier is determined by \field{flags}. The > > > > +3 most significant bits of \field{can_id} do not bear the information > > > > +about the type of the CAN message identifier and are 0. > > > > + > > > > +The device MUST reject any CAN frame type for which support has not been > > > > +negotiated with VIRTIO_CAN_RESULT_NOT_OK in \field{result} and MUST NOT > > > > +schedule the message for transmission. A CAN frame with an undefined bit > > > > +set in \field{flags} is treated like a CAN frame for which support has > > > > +not been negotiated. > > > > + > > > > +The device MUST reject any CAN frame for which \field{can_id} or > > > > +\field{sdu} length are out of range or the CAN controller is in an > > > > +invalid state with VIRTIO_CAN_RESULT_NOT_OK in \field{result} and MUST > > > > +NOT schedule the message for transmission. > > > > + > > I am not very familiar with CAN but how does the device figure out that > > the can_id is out of range? > > In classical CAN we have the standard CAN frames, which have an 11 bit > ID, and there are extended CAN frames, which have 29 bits ID. Extended > frames are signaled with VIRTIO_CAN_FLAGS_EXTENDED set. > > So if a standard frame uses more than 11 Bits of CAN-ID, it's considered > out of range. > Thanks Marc for the explanation. Do you think that it would be worthwhile to add that to the spec at some point? Matias. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org