09.11.2020 17:53, Mikko Perttunen пишет:
...
> I guess for the channel_map we can drop the offset/length, I just think
> it's fairly obvious that an IOMMU mapping API lets you specify from
> where and how much you want to map. Sure, it's not a functionality
> blocker as it can simply be
On 10/31/20 1:13 AM, Dmitry Osipenko wrote:
28.10.2020 12:54, Mikko Perttunen пишет:
On 10/27/20 9:06 PM, Dmitry Osipenko wrote:
26.10.2020 12:11, Mikko Perttunen пишет:
The first patches should be the ones that are relevant to the existing
userspace code, like support for the waits.
Can
28.10.2020 12:54, Mikko Perttunen пишет:
> On 10/27/20 9:06 PM, Dmitry Osipenko wrote:
>> 26.10.2020 12:11, Mikko Perttunen пишет:
The first patches should be the ones that are relevant to the existing
userspace code, like support for the waits.
>>>
>>> Can you elaborate what you
On 10/27/20 9:06 PM, Dmitry Osipenko wrote:
26.10.2020 12:11, Mikko Perttunen пишет:
The first patches should be the ones that are relevant to the existing
userspace code, like support for the waits.
Can you elaborate what you mean by this?
All features that don't have an immediate real
26.10.2020 12:11, Mikko Perttunen пишет:
>>
>> The first patches should be the ones that are relevant to the existing
>> userspace code, like support for the waits.
>
> Can you elaborate what you mean by this?
All features that don't have an immediate real use-case should be placed
later in the
On 10/22/20 7:20 AM, Dmitry Osipenko wrote:
20.10.2020 12:18, Mikko Perttunen пишет:
I'm asking this question because right now there is only one potential
client for this IOCTL, the VIC. If other clients aren't supposed to be a
part of the DRM driver, like for example NVDEC which probably
20.10.2020 12:18, Mikko Perttunen пишет:
>> I'm asking this question because right now there is only one potential
>> client for this IOCTL, the VIC. If other clients aren't supposed to be a
>> part of the DRM driver, like for example NVDEC which probably should be
>> a V4L driver, then DRM driver
On 10/20/20 2:40 PM, Daniel Vetter wrote:
On Mon, Oct 19, 2020 at 7:27 PM Dmitry Osipenko wrote:
19.10.2020 11:13, Mikko Perttunen пишет:
On 10/19/20 5:21 AM, Dmitry Osipenko wrote:
07.10.2020 20:12, Mikko Perttunen пишет:
+int tegra_drm_ioctl_channel_map(struct drm_device *drm, void
On Mon, Oct 19, 2020 at 7:27 PM Dmitry Osipenko wrote:
>
> 19.10.2020 11:13, Mikko Perttunen пишет:
> > On 10/19/20 5:21 AM, Dmitry Osipenko wrote:
> >> 07.10.2020 20:12, Mikko Perttunen пишет:
> >>> +int tegra_drm_ioctl_channel_map(struct drm_device *drm, void *data,
> >>> +
On 10/19/20 8:27 PM, Dmitry Osipenko wrote:
19.10.2020 11:13, Mikko Perttunen пишет:
On 10/19/20 5:21 AM, Dmitry Osipenko wrote:
07.10.2020 20:12, Mikko Perttunen пишет:
+int tegra_drm_ioctl_channel_map(struct drm_device *drm, void *data,
+ struct drm_file *file)
+{
Hello,
07.10.2020 20:12, Mikko Perttunen пишет:
> +int tegra_drm_ioctl_channel_map(struct drm_device *drm, void *data,
> + struct drm_file *file)
> +{
Hello, Mikko!
Could you please tell what are the host1x clients that are going to be
upstreamed and will need this IOCTL?
19.10.2020 11:13, Mikko Perttunen пишет:
> On 10/19/20 5:21 AM, Dmitry Osipenko wrote:
>> 07.10.2020 20:12, Mikko Perttunen пишет:
>>> +int tegra_drm_ioctl_channel_map(struct drm_device *drm, void *data,
>>> + struct drm_file *file)
>>> +{
>>
>> Hello, Mikko!
>>
>> Could you please
On 10/19/20 5:21 AM, Dmitry Osipenko wrote:
07.10.2020 20:12, Mikko Perttunen пишет:
+int tegra_drm_ioctl_channel_map(struct drm_device *drm, void *data,
+ struct drm_file *file)
+{
Hello, Mikko!
Could you please tell what are the host1x clients that are going
Hi Mikko,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tegra-drm/drm/tegra/for-next]
[also build test ERROR on tegra/for-next linus/master v5.9-rc8 next-20201007]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
14 matches
Mail list logo
