Displaying 20 results from an estimated 156 matches for "nuernberger".
Did you mean:
nuernberg
2018 Oct 22
1
OPUS at Texas Instruments C6418
Hi Jean-Marc,
thank you for that suggestion!
It seems that the file "fixed_c6x.h" is not part of the Opus sources, so the compiler cannot find it after enabling the TI_C6X_ASM config option.
Maybe it was only part of an early version of the Opus sources?
I looked for the file in versions V1.1, V1.1.1, V1.2alpha and V1.3 but did not found it.
Do you have an idea, where I can get the
2018 Oct 19
2
OPUS at Texas Instruments C6418
Dear Opus family,
we have implemented the Opus codec at a Texas Instruments DSP C6418.
It is working fine!
Does anyone has experience with the configuration of the codec for a speed optimized implementation on that DSP?
At the moment, we use the following settings:
#define NONTHREADSAFE_PSEUDOSTACK 1
#define FIXED_POINT
2001 Aug 08
2
Executable size with vorbis.
...there anything
we could cut out to make them smaller? I threw all of the code into one
static lib and (after fixing quite a few compiler errors) noticed that the
resulting lib was around 600k. Too large for a downloadable that is already
over 1 meg.
Any ideas would be greatly appreciated. Chris Nuernberger
(chris.nuernberger@anark.com).
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject...
2018 Oct 22
0
OPUS at Texas Instruments C6418
Hi Robert,
The file is not distributed in the official releases, but I can find it
in the git repository.
Cheers,
Jean-Marc
On 10/22/2018 03:53 AM, Robert Madinger wrote:
> Hi Jean-Marc,
>
> thank you for that suggestion!
> It seems that the file "fixed_c6x.h" is not part of the Opus sources, so the compiler cannot find it after enabling the TI_C6X_ASM config option.
2025 Jan 13
0
[PATCH v2 02/25] drm/dumb-buffers: Provide helper to set pitch and size
Hi
Am 13.01.25 um 04:53 schrieb Andy Yan:
[...]
>> Thanks for taking a look. That NV-related code at [0] is a 'somewhat
>> non-idiomatic use' of the UAPI. The dumb-buffer interface really just
>> supports a single plane. The fix would be a new ioctl that takes a DRM
>> 4cc constant and returns a buffer handle/pitch/size for each plane. But
>> that's
2005 Jan 28
1
tdb_fetch failed on Printer Share
Hi,
after some Tests with Printer Driver Upload after an Upgrade from Samba
2.4 to 3.0 i found this Infos in the samba Log:
[2005/01/28 19:21:03, 1] smbd/service.c:make_connection_snum(648)
mic-nuernberg (172.30.10.7) connect to service print$ initially as
user reiss
(uid=1000, gid=1007) (pid 14785)
[2005/01/28 19:21:03, 1] smbd/service.c:close_cnum(836)
mic-nuernberg (172.30.10.7) closed
2008 Apr 29
0
Strange behaviour regarding timestamps when copying files
Hi all,
we observed a strange effect when copying an file within a samba
share: Both atime an mtime of the target file are set to the mtime
of the original file. The atime of the original file is updated to
the current time.
1. Status of the original file:
# stat test.txt
File: `test.txt'
Size: 3 Blocks: 8 IO Block: 4096 regular file
Device: 811h/2065d
2019 May 03
2
[PATCH v3 01/19] drm: Add |struct drm_gem_vram_object| and helpers
Am 03.05.19 um 14:01 schrieb Daniel Vetter:
> [CAUTION: External Email]
>
> On Fri, May 3, 2019 at 12:15 PM Thomas Zimmermann <tzimmermann at suse.de> wrote:
>> Hi Christian,
>>
>> would you review the whole patch set? Daniel mentioned that he'd prefer
>> to leave the review to memory-mgmt developers.
> I think Noralf Tronnes or Gerd Hoffmann would
2019 May 03
2
[PATCH v3 01/19] drm: Add |struct drm_gem_vram_object| and helpers
Am 03.05.19 um 14:01 schrieb Daniel Vetter:
> [CAUTION: External Email]
>
> On Fri, May 3, 2019 at 12:15 PM Thomas Zimmermann <tzimmermann at suse.de> wrote:
>> Hi Christian,
>>
>> would you review the whole patch set? Daniel mentioned that he'd prefer
>> to leave the review to memory-mgmt developers.
> I think Noralf Tronnes or Gerd Hoffmann would
2019 Sep 03
1
[PATCH 4/5] drm/qxl: use drm_gem_object_funcs callbacks
On Mon, Sep 02, 2019 at 04:34:49PM +0200, Thomas Zimmermann wrote:
> This patch seems unrelated.
Well, patch 5/5 depends on it because it hooks the
drm_gem_ttm_print_info helper into the new
qxl_object_funcs added by this patch.
> Am 02.09.19 um 14:41 schrieb Gerd Hoffmann:
> > Switch qxl to use drm_gem_object_funcs callbacks
> > instead of drm_driver callbacks.
> >
>
2025 Jan 16
3
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi,
On 16/01/2025 10:09, Thomas Zimmermann wrote:
> Hi
>
>
> Am 15.01.25 um 15:20 schrieb Tomi Valkeinen:
> [...]
>>
>> My point is that we have the current UAPI, and we have userspace using
>> it, but we don't have clear rules what the ioctl does with specific
>> parameters, and we don't document how it has to be used.
>>
>> Perhaps
2002 Sep 24
5
BUG: ssh hangs on full stdout-file-system
System: Linux 2.4.18, openssh-3.4p1
Problem:
I use "ssh" and "tar" to backup remote directory trees to a local
hard-disk/file-system:
# ssh remote.server.org "tar -cz /home" >/backup/remote.tar.gz
If the backup-file-system runs out of space before the backup
completes, ssh starts hanging (waiting for the stdout-write to
complete).
Analysis:
In
2024 Aug 12
1
[PATCH v2 1/9] drm: Do delayed switcheroo in drm_lastclose()
Hi
Am 12.08.24 um 12:18 schrieb Daniel Vetter:
> On Mon, Aug 12, 2024 at 11:23:44AM +0200, Daniel Vetter wrote:
>> On Mon, Aug 12, 2024 at 10:28:22AM +0200, Thomas Zimmermann wrote:
>>> Amdgpu and nouveau call vga_switcheroo_process_delayed_switch() from
>>> their lastclose callbacks. Call it from drm_lastclose(), so that the
>>> driver functions can finally be
2002 Mar 31
1
How to get the datapoints of an density estimationwithlocfit?
Hello!!
At first thank you all for your suggestions and your help.
But I would like to get another group of datas from the density estimation. I don't know if these information are provided by locfit or I should use an other function like plot().
Description:
Each number between 1 and 100 (only integer) for example should have only one density value. But I also would like to have the density
2024 Aug 12
1
[PATCH v2 1/9] drm: Do delayed switcheroo in drm_lastclose()
On Mon, Aug 12, 2024 at 12:41:39PM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 12.08.24 um 12:18 schrieb Daniel Vetter:
> > On Mon, Aug 12, 2024 at 11:23:44AM +0200, Daniel Vetter wrote:
> > > On Mon, Aug 12, 2024 at 10:28:22AM +0200, Thomas Zimmermann wrote:
> > > > Amdgpu and nouveau call vga_switcheroo_process_delayed_switch() from
> > > > their
2024 Aug 12
1
[PATCH v2 5/9] drm/nouveau: Implement switcheroo reprobe with drm_client_dev_hotplug()
On 8/12/24 10:28 AM, Thomas Zimmermann wrote:
> Replace the call to drm_fb_helper_output_poll_changed() with a call
> to drm_client_dev_hotplug(). It is equivalent in functionality, but
> uses the DRM client infrastructure.
>
> v2:
> - fix commit description
>
> Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>
> Reviewed-by: Daniel Vetter
2024 Aug 12
1
[PATCH v2 5/9] drm/nouveau: Implement switcheroo reprobe with drm_client_dev_hotplug()
Hi
Am 12.08.24 um 14:17 schrieb Danilo Krummrich:
> On 8/12/24 10:28 AM, Thomas Zimmermann wrote:
>> Replace the call to drm_fb_helper_output_poll_changed() with a call
>> to drm_client_dev_hotplug(). It is equivalent in functionality, but
>> uses the DRM client infrastructure.
>>
>> v2:
>> - fix commit description
>>
>> Signed-off-by: Thomas
2024 Sep 09
1
[PATCH v4 71/80] drm/vmwgfx: Run DRM default client setup
On Mon, Sep 9, 2024 at 7:37?AM Thomas Zimmermann <tzimmermann at suse.de> wrote:
>
> Call drm_client_setup() to run the kernel's default client setup
> for DRM. Set fbdev_probe in struct drm_driver, so that the client
> setup can start the common fbdev client.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>
> Cc: Zack Rusin <zack.rusin at
2025 Jan 20
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi
Am 16.01.25 um 11:03 schrieb Tomi Valkeinen:
[...]
> Aligning video= and dumb buffers almost sounds like going backwards.
> video= parameter is bad,
Who told you that? Video= is still the way to specify an initial display
mode to the kernel and it will remain so.
Of course, it is better to auto-detect settings, but that's for a
different use case.
Best regards
Thomas
>
2025 Jan 20
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi,
On 20/01/2025 09:49, Thomas Zimmermann wrote:
> Hi
>
>
> Am 16.01.25 um 11:03 schrieb Tomi Valkeinen:
> [...]
>> Aligning video= and dumb buffers almost sounds like going backwards.
>> video= parameter is bad,
>
> Who told you that? Video= is still the way to specify an initial display
> mode to the kernel and it will remain so.
You did =). "It