public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Cc: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	 Henning Schild <henning.schild@siemens.com>
Subject: ISAR evaluation nVidia image generator based on Debian bullseye
Date: Wed, 5 Oct 2022 13:35:19 +0200	[thread overview]
Message-ID: <CAJGKYO4eZ=5eKt6CCKzfRF0XUNdbin+KwJ3ex0Dx0nQzsMgmhQ@mail.gmail.com> (raw)

Dear all,

I am proud to announce the v0.9.1 of an ISAR evaluation nVidia image
generator based on Debian bullseye. I hardly believe that this project
will surprise you because of the technology adopted nor its use but
probably you will find this file interesting, in particular the
rationale chapter.

https://github.com/robang74/isar-nvidia-debian/blob/main/README.md

It is an original rework of code based only on published source code
and recipes. At the moment, this project is locked on a specific
version of the driver (515.65.01) and CUDA libraries (11.7). It is my
desire that it remains in this state for a purpose because it is just
a proof of concept (PoC) and not even a commercial demo. Thanks in
advance.

I have no hardware with a supported nVidia card. It is appreciated
that someone will take a nvidia-smi test on a complete or nvdocker
image. The feedback would be appreciated also in private form. For
this reason this project should be considered untested.

 After all, at the console login screen and immediately after a
message of no warranty granted but delivered AS-IS is always
displayed.

 Have fun! <3

 Best regards, R-

             reply	other threads:[~2022-10-05 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 11:35 Roberto A. Foglietta [this message]
2022-10-05 22:01 ` Roberto A. Foglietta
2022-10-09 21:12 ` Roberto A. Foglietta

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='CAJGKYO4eZ=5eKt6CCKzfRF0XUNdbin+KwJ3ex0Dx0nQzsMgmhQ@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox