From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: dariobin@libero.it, Jacob Kroon <jacob.kroon@gmail.com>,
linux-can@vger.kernel.org, wg@grandegger.com
Subject: Re: CM-ITC, pch_can/c_can_pci, sendto() returning ENOBUFS
Date: Wed, 21 Sep 2022 13:00:52 +0200 [thread overview]
Message-ID: <2ff63f6f-a952-9ead-91a4-a98ad4c3a7ca@hartkopp.net> (raw)
In-Reply-To: <20220921105351.peoyk2a64ayd27gj@pengutronix.de>
On 21.09.22 12:53, Marc Kleine-Budde wrote:
> On 21.09.2022 12:39:06, Oliver Hartkopp wrote:
>>
>>
>> On 21.09.22 12:32, Marc Kleine-Budde wrote:
>>> On 21.09.2022 11:55:59, Oliver Hartkopp wrote:
>>>> Btw. I uploaded the 'latest' C_CAN manuals on
>>>>
>>>> https://github.com/linux-can/can-doc
>>>>
>>>> ... as it could only be found on archive.org :-/
>>>>
>>>> Unfortunately I was not able to find any (latest?) D_CAN manual anymore,
>>>> which was originally hosted at http://www.semiconductors.bosch.de/media/en/pdf/ipmodules_1/can/d_can_users_manual_111.pdf
>>>>
>>>> Archive.org did not crawl this PDF ;-(
>>>>
>>>> If someone still has this D_CAN PDF please send a URL or the PDF itself to
>>>> me, so that I can put it there too.
>>>
>>> I've found some old stuff on https://www.yumpu.com/user/bosch.semiconductors.de
>>>
>>> You've got PR:
>>> https://github.com/linux-can/can-doc/pull/1
>>
>> Pulled.
>>
>> Excellent contribution! Thanks Marc!
>
> Doh! I accidentally committed the readme of your M_CAN history repo.
> I'll force push the master to get rid of it. OK?
NP. Just go for it ;-)
next prev parent reply other threads:[~2022-09-21 11:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 13:25 CM-ITC, pch_can/c_can_pci, sendto() returning ENOBUFS Jacob Kroon
2022-08-26 11:24 ` Jacob Kroon
2022-08-29 9:14 ` Jacob Kroon
2022-08-29 13:20 ` Jacob Kroon
2022-08-29 13:53 ` Oliver Hartkopp
2022-08-30 12:59 ` Jacob Kroon
2022-08-30 19:15 ` Oliver Hartkopp
2022-09-01 9:38 ` Jacob Kroon
2022-09-01 16:35 ` Oliver Hartkopp
2022-09-02 15:13 ` Jacob Kroon
2022-09-02 16:39 ` Jacob Kroon
2022-09-05 14:17 ` Marc Kleine-Budde
2022-09-05 15:54 ` Marc Kleine-Budde
2022-09-16 4:14 ` Jacob Kroon
2022-09-19 23:24 ` Jacob Kroon
2022-09-20 1:23 ` Vincent Mailhol
2022-09-20 5:08 ` Jacob Kroon
2022-09-21 7:25 ` dariobin
2022-09-21 7:47 ` Marc Kleine-Budde
2022-09-21 8:26 ` Jacob Kroon
2022-09-21 9:55 ` Oliver Hartkopp
2022-09-21 10:32 ` Marc Kleine-Budde
2022-09-21 10:39 ` Oliver Hartkopp
2022-09-21 10:53 ` Marc Kleine-Budde
2022-09-21 11:00 ` Oliver Hartkopp [this message]
2022-09-22 7:20 ` dariobin
2022-09-23 11:36 ` Marc Kleine-Budde
2022-09-23 17:55 ` dariobin
2022-09-23 19:03 ` Jacob Kroon
2022-09-23 19:21 ` Jacob Kroon
2022-09-23 19:45 ` dariobin
2022-09-23 20:27 ` Jacob Kroon
2022-09-24 5:17 ` Jacob Kroon
2022-09-28 8:25 ` Marc Kleine-Budde
2022-09-28 8:28 ` Jacob Kroon
2022-09-28 8:02 ` Marc Kleine-Budde
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=2ff63f6f-a952-9ead-91a4-a98ad4c3a7ca@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=dariobin@libero.it \
--cc=jacob.kroon@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=wg@grandegger.com \
/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 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.