similar to: CDR MEDIA

Displaying 20 results from an estimated 4000 matches similar to: "CDR MEDIA"

2008 Jan 19
1
Set Return Type XML in Prototype
Please help i can''t return xml data using prototype. If i use data from direct xml file then it works fine but when i use ajax request with header content xml it''s not working My code just work on IE but in FF it does not working. My code sample are given below If any one already done this kinds of job Please help me as soon as possible. var xmlDoc; function Claulate() { var
2023 Apr 09
1
extracting pdf tables...
Dear members, I am extracting a pdf table by the following code: > library(tabulizer) > IDT <- extract_tables("https://www.canmoney.in/pdf/INTRADAYLEVERAGE-20220531-latest.pdf",output = "data.frame") It returns 4 different data frames which I want to combine them and make one data frame. But when I run this: >
2020 Aug 24
0
[PATCH v6 36/76] x86/head/64: Load IDT earlier
From: Joerg Roedel <jroedel at suse.de> Load the IDT right after switching to virtual addresses in head_64.S so that the kernel can handle #VC exceptions. Signed-off-by: Joerg Roedel <jroedel at suse.de> Link: https://lore.kernel.org/r/20200724160336.5435-36-joro at 8bytes.org --- arch/x86/include/asm/setup.h | 3 +++ arch/x86/kernel/head64.c | 3 +++ arch/x86/kernel/head_64.S
2020 Aug 24
0
[PATCH v6 42/76] x86/sev-es: Setup early #VC handler
From: Joerg Roedel <jroedel at suse.de> Setup an early handler for #VC exceptions. There is no GHCB mapped yet, so just re-use the vc_no_ghcb_handler. It can only handle CPUID exit-codes, but that should be enough to get the kernel through verify_cpu() and __startup_64() until it runs on virtual addresses. Signed-off-by: Joerg Roedel <jroedel at suse.de> Link:
2023 Apr 09
1
extracting pdf tables...
Clearly the column names are different. You need to decide what to do about that. Choose the subset of dataframes where the column names are the same? Rename columns? Omit some columns? Add missing columns filled with NA? On April 9, 2023 10:22:32 AM PDT, akshay kulkarni <akshay_e4 at hotmail.com> wrote: >Dear members, > I am extracting a pdf table by the
2020 Jul 14
0
[PATCH v4 29/75] x86/idt: Move two function from k/idt.c to i/a/desc.h
From: Joerg Roedel <jroedel at suse.de> Move these two functions from kernel/idt.c to include/asm/desc.h: * init_idt_data() * idt_init_desc() These functions are needed to setup IDT entries very early and need to be called from head64.c. To be usable this early these functions need to be compiled without instrumentation and the stack-protector feature. These features need to be kept
2020 Feb 11
0
[PATCH 23/62] x86/idt: Move IDT to data segment
From: Joerg Roedel <jroedel at suse.de> With SEV-ES, exception handling is needed very early, even before the kernel has cleared the bss segment. In order to prevent clearing the currently used IDT, move the IDT to the data segment. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- arch/x86/kernel/idt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git
2020 Jul 14
0
[PATCH v4 27/75] x86/idt: Move IDT to data segment
From: Joerg Roedel <jroedel at suse.de> With SEV-ES, exception handling is needed very early, even before the kernel has cleared the bss segment. In order to prevent clearing the currently used IDT, move the IDT to the data segment. Signed-off-by: Joerg Roedel <jroedel at suse.de> --- arch/x86/kernel/idt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git
2023 Apr 09
1
extracting pdf tables...
Dear Jeff, Thanks for your reply. I have the following: > colnames(IDT[[4]]) [1] "X168" "TATA.MOTORS.LIMITED" "TATAMOTORS" "X4" THe above has to be the first row of IDT[[4]]. The first row is getting parsed as the column name. How do you make that the first row of IDT[[4]]? Thanking you, Yours sincerely,
2023 Apr 09
1
extracting pdf tables...
Dear Jeff, I want to rbind. Thanking you, Yours sincerely, AKSHAY M KULKARNI ________________________________ From: R-help <r-help-bounces at r-project.org> on behalf of Jeff Newmiller <jdnewmil at dcn.davis.ca.us> Sent: Sunday, April 9, 2023 11:57 PM To: r-help at r-project.org <r-help at r-project.org> Subject: Re: [R] extracting pdf tables... Sorry, did not
1997 Nov 13
0
Linux F00F Patch [Forwarded e-mail from Aleph One]
[mod: The first message would''ve been rejected on the grounds "no security related information", but it gives ME a warm feeling too, so I''m allowing it to piggyback on the announcement of the "fix". Note that Linux-2.1.63 simply implements a fix for the problem, instead of applying this fix, upgrading to 2.1.63 might be an option for you. Linus indicated that
2013 Apr 08
3
[PATCH] x86: make IDT read-only
This makes the IDT unconditionally read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks. It has an added benefit of also not leaking (via the "sidt" instruction) the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> ---
2013 Apr 08
3
[PATCH] x86: make IDT read-only
This makes the IDT unconditionally read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks. It has an added benefit of also not leaking (via the "sidt" instruction) the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> ---
2020 Aug 31
2
[PATCH v6 42/76] x86/sev-es: Setup early #VC handler
On Mon, Aug 24, 2020 at 10:54:37AM +0200, Joerg Roedel wrote: > +#ifdef CONFIG_AMD_MEM_ENCRYPT > +static void set_early_idt_handler(gate_desc *idt, int n, void *handler) > +{ > + struct idt_data data; > + gate_desc desc; > + > + init_idt_data(&data, n, handler); > + idt_init_desc(&desc, &data); > + native_write_idt_entry(idt, n, &desc); > +} >
2020 Aug 31
2
[PATCH v6 42/76] x86/sev-es: Setup early #VC handler
On Mon, Aug 24, 2020 at 10:54:37AM +0200, Joerg Roedel wrote: > +#ifdef CONFIG_AMD_MEM_ENCRYPT > +static void set_early_idt_handler(gate_desc *idt, int n, void *handler) > +{ > + struct idt_data data; > + gate_desc desc; > + > + init_idt_data(&data, n, handler); > + idt_init_desc(&desc, &data); > + native_write_idt_entry(idt, n, &desc); > +} >
2008 May 24
2
Importing data in text file into R
Dear all, I am quite new to R; facing certain problems: Say, I have a text file( named as "try"): Year C1 C2 C3 C4 C5 C6 Y1 3.5 13.8 9.5 6.8 0.4 24.2 Y2 3.8 13.9 9.9 7.6 0.7 12.8 Y3 4.5 14.5 14.2 9.2 0.6 14.5 Y4 5.9 16.2 24.6 12.7 0.2 24.3 Y5 7.2 20.4 40.6 18.2 0.8 28.2 Y6 5.9 18.6 37.4 14.5 0.3 36.9 Y7 8.0 16.1 88.6 24.1 0.1 34.6 Y8 13.6 21.1 56.3 19.0 0.7 33.3 I wish to import the
2020 Jul 14
0
[PATCH v4 28/75] x86/idt: Split idt_data setup out of set_intr_gate()
From: Joerg Roedel <jroedel at suse.de> The code to setup idt_data is needed for early exception handling, but set_intr_gate() can't be used that early because it has pv-ops in its code path, which don't work that early. Split out the idt_data initialization part from set_intr_gate() so that it can be used separatly. Signed-off-by: Joerg Roedel <jroedel at suse.de> ---
2020 Aug 24
0
[PATCH v6 29/76] x86/idt: Split idt_data setup out of set_intr_gate()
From: Joerg Roedel <jroedel at suse.de> The code to setup idt_data is needed for early exception handling, but set_intr_gate() can't be used that early because it has pv-ops in its code path, which don't work that early. Split out the idt_data initialization part from set_intr_gate() so that it can be used separatly. Signed-off-by: Joerg Roedel <jroedel at suse.de>
2013 Apr 09
2
[PATCH v2] x86: use fixed read-only IDT
Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> --- v2: - clarify commit
2013 Apr 09
2
[PATCH v2] x86: use fixed read-only IDT
Make a copy of the IDT (as seen via the "sidt" instruction) read-only. This primarily removes the IDT from being a target for arbitrary memory write attacks, and has the added benefit of also not leaking the kernel base offset, if it has been relocated. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Eric Northup <digitaleric at google.com> --- v2: - clarify commit